Detailed Analysis
A Reddit user on Anthropic's Claude Team plan has surfaced a discoverability issue with "Record a Skill," a feature designed to let users capture their workflow interactions within Cowork and convert them into reusable Claude Skills. Despite being an org admin running the latest version of the Windows desktop app and confirming Cowork itself functions normally, the poster cannot locate the feature anywhere in the interface—not in the "+" menu, not under Skills > Manage skills, and unsurprisingly not on web or mobile, where the feature is known to be unsupported. The user's troubleshooting steps (updating the app, restarting, checking multiple menu locations) suggest a genuine attempt to rule out user error before concluding this may be a rollout gap rather than a configuration problem.
This kind of report is emblematic of the friction that often accompanies staggered feature rollouts at fast-moving AI companies. Anthropic has been rapidly expanding Claude's capabilities beyond conversational chat into more agentic, workflow-oriented territory, with Cowork and Skills representing part of that push toward making Claude a collaborative tool embedded in real work processes rather than a standalone chatbot. "Record a Skill" specifically lowers the barrier to creating custom Skills by letting users demonstrate a task rather than manually write instructions—a meaningfully different UX paradigm than static prompt engineering. When such a feature is announced but appears unevenly across seemingly identical account tiers (Team plan, admin permissions, updated desktop client), it creates confusion about whether the rollout is intentionally gradual, gated by additional flags, or simply buggy.
The lack of clear rollout communication matters because Team and Enterprise customers represent Anthropic's highest-value, most operationally-dependent user base. When admins can't determine whether a missing feature is a settings issue, a permissions issue, or a staged deployment, it creates support burden and erodes confidence in feature announcements, especially for organizations trying to plan workflows around new capabilities. This is a recurring pattern across the AI industry: companies like OpenAI, Google, and Anthropic frequently announce features that roll out in waves—sometimes by account type, sometimes by geography, sometimes by A/B test cohort—without always making the rollout status transparent to end users in real time.
More broadly, this incident reflects the growing pains of an industry moving quickly to ship agentic features (Skills, Cowork, computer-use capabilities) that are more complex to deploy uniformly than simple model updates. As Claude and competing platforms push toward more autonomous, workflow-embedded tooling, the operational complexity of rollout management—version gating, plan-tier restrictions, platform-specific availability—becomes a visible pain point for power users and admins who expect consistency across supposedly equivalent accounts. Threads like this one on r/ClaudeAI function as informal bug-triage and rollout-status channels, filling a communication gap that official changelogs and release notes don't always address in real time.
Read original article →