Detailed Analysis
A Reddit user's post on r/ClaudeAI highlights growing user interest in operationalizing Claude Co-work for professional workflows, specifically around UX research tasks such as generating user testing interview guides. The user reports two distinct friction points: unexpectedly high capacity consumption when building and reusing skills, and an inability to host or dynamically edit the markdown documents that underpin those skills. The post reflects a broader pattern of early adopters moving past exploratory usage and attempting to industrialize Claude into repeatable, scalable workflows — a transition that exposes gaps between the platform's current capabilities and the demands of production-grade professional use.
On the question of skill capacity and consumption, the user's experience is consistent with known constraints of the Co-work environment. Skills built on large, structured markdown files combined with multiple reference examples carry significant context overhead, and reusing them repeatedly draws against daily usage limits because each invocation loads that full context anew. The research context confirms a well-established best practice: chunking skills into narrow, focused modules rather than building monolithic ones. A single skill attempting to handle all aspects of interview guide generation — persona, structure, tone, and formatting — will degrade in performance and consume more capacity than several tightly scoped skills linked sequentially. Anthropic's own guidance and practitioner guides recommend placing overarching instructions in a dedicated `CLAUDE.md` file to govern outputs consistently across skills, reducing redundant context loading and improving throughput efficiency.
The document hosting question reveals a more fundamental architectural limitation in the current Co-work implementation. As of April 2026, Claude Co-work reads files and folders from user-organized local or project-specific directories and can adapt skill outputs to different surfaces — generating Word documents, Excel breakdowns, or PowerPoint files depending on context — but the dynamic, real-time document update loop the user describes is not fully supported out of the box. Practitioners working around this limitation typically maintain a dedicated project folder structure that Claude accesses directly, editing source files locally and relying on Claude to re-read updated versions at the start of each session. This is a workaround rather than a native solution, and it places the document versioning burden on the user rather than the system.
These friction points connect to a broader trend in enterprise AI adoption: the gap between demonstration-grade capability and production-grade reliability. Co-work was designed to reduce the barrier to automation by enabling non-coders to build skills through natural language description and workflow recording, but scaling those skills for daily professional use — with consistent output quality, predictable resource consumption, and dynamic data integration — requires a level of infrastructure thinking that the platform has not yet fully abstracted away. The Team and Enterprise plans address part of this through centralized skill sharing and organizational provisioning, but individual users on standard plans face meaningful constraints when attempting to build the kind of robust, iterative research tooling the Reddit poster envisions.
Anthropic's trajectory with Co-work suggests these limitations are transitional rather than permanent. The platform's support for app connectors, scheduling, and multi-agent delegation via sub-agents indicates a roadmap oriented toward deeper workflow integration, and the growing ecosystem of practitioner guides and community tutorials reflects accelerating real-world experimentation. As users like the original poster push the boundaries of what Co-work can support, their documented friction points effectively function as product feedback that shapes the platform's evolution. The convergence of AI capability with the operational demands of knowledge workers — UX researchers, content strategists, analysts — represents one of the most active frontiers in applied AI development, and Co-work's early-adopter community is serving as both test bed and proof-of-concept for what industrialized AI assistance might look like at scale.
Read original article →