On July 21, Anthropic launched Record a Skill in the "+" menu of Cowork on the Claude desktop app: as you work on your computer and narrate aloud, Claude automatically distills the recorded demo into a reusable skill (a skill file). It is the shortest path to turning the team workflows that "only the veteran knows, answers only when asked, and nobody wants to write down" into AI-executable assets. Previously, creating a skill meant hand-writing a Markdown SKILL.md — a high bar for non-technical people; teaching by screen recording skips the "write documentation" step entirely. The feature is currently open to Pro, Max, and Team subscribers.

The Core Problem It Solves: Tacit Experience → Explicit Skill

Most coverage files Record a Skill under "a more convenient way to create automations," but that reading stops at the surface.

The real barrier to hand-writing a skill was never Markdown syntax — it was translating tacit experience into explicit instructions. When experts make judgment calls, they naturally reveal: which cases to skip, which format is a hard client requirement, which anomalous number needs a human double-check. These things are hard to write into an operations manual, but a "do it while narrating" screen recording preserves them completely.

Record a Skill captures screen actions and voice narration together, and the narration is the key — it bypasses the "writing" step, so doing it once and explaining it once is enough. For enterprise knowledge management, this solves the decades-old "experts won't write documentation" problem with the least friction possible.

Generate Your Own Skill in Three Steps

Step 1: Find the Entry Point

Open the Claude desktop client and click through from the bottom-left of the Cowork chat box:

[+] → Skills → Manage skills → Add → Record your screen

On first use, the system will request screen recording and microphone permissions; after allowing them, click Start Recording to begin.

💡 Pitfall to avoid: never expose plaintext passwords, keys, API keys, credit card numbers, or other sensitive information during recording. Claude uses everything it captures on screen as analysis material, and once recorded there is no taking it back.

Step 2: Demo the Full Workflow Once

On your computer, run the workflow you want to capture from start to finish while narrating the necessary implicit logic aloud. A few pointers:

• Cover it completely: do not skip steps, even ones that look irrelevant like "refreshing the page while waiting for results."
• Explain the judgment calls: at branching decisions, say out loud "in this case I usually pick A, because..."
• Avoid unrelated actions: do not switch over to watch videos or reply to messages mid-recording — those pollute Claude's understanding of the workflow.

After clicking "stop recording," you return to the Claude Cowork interface for analysis and skill distillation.

Step 3: Save and Invoke with a Slash Command

Once the analysis finishes, your custom skill is generated. Click Save Skill to deploy it straight into Claude. From then on, type the slash command / in any conversation to invoke the skill and put it to work for you.

No repeated fine-tuning — the freshly generated skill works out of the box.

Verifying It Worked

Success looks like this: your newly recorded skill shows up in the Manage skills list, usually named automatically by Claude based on the recording. Start a new conversation, type /, and you can find it in the command list and correctly trigger the full workflow.

If the generated skill misses steps or gets the judgment logic wrong, delete and re-record once — the cost is negligible.

How It Differs from Hand-Writing a Skill

Use Cases

• Operations handoffs: record the monthly content-calendar generation flow as a skill, and new hires or clients can run it themselves.
• Customer support: codify the standard actions of "when a ticket arrives: classify it, search the knowledge base, draft a reply."
• Data processing: fixed-format report cleaning, aggregation, and charting — record once, reuse repeatedly.
• Design standards: hard requirements for brand fonts, color palettes, and export ratios; once recorded into a skill, the AI stops drifting from them.

FAQ

• Where do I grant screen recording permission?: the first click of Start Recording pops the system authorization dialog. If you accidentally hit deny, re-authorize Claude under macOS System Settings → Privacy & Security → Screen Recording / Microphone.
• The generated skill is not accurate — now what?: delete and re-record, narrating more of the judgment logic and doing fewer unrelated actions.
• Which subscriptions can use it?: currently only the Pro, Max, and Team plans; Free users do not have access yet.
• Can I edit the generated skill?: yes — after saving you can view and modify its underlying definition in Manage skills.