Verdict: Claude's "Record a Skill" feature, launched July 21, 2026, eliminates the hardest part of automating repeatable work: writing the instructions. You perform a task on screen, narrate your reasoning out loud, and Claude converts the demonstration into a reusable skill it can run again without further prompting. It works inside Claude Cowork on Mac for Pro, Max, and Team subscribers. The catch: most people skip the testing step and trust a skill that captured accidental specifics from their demo instead of the actual rule. Here is how to use it correctly.
Last verified: 2026-07-29
- Record a Skill lives in the Claude desktop app's Cowork workspace, behind the "+" menu
- Available on Pro ($20/mo), Max 5x ($100/mo), Max 20x (~$200/mo), and Team plans
- Mac only at launch; not available on Windows, web, mobile, Free, or Enterprise plans
- ~10-minute recording limit; video and audio are NOT retained after processing
- Skills built this way work across Claude.ai, Claude Code, and the API
What Is Claude Record a Skill and How Does It Work?
Record a Skill is a screen-recording-based skill-creation tool inside Claude Cowork. Instead of writing a prompt or manually authoring a SKILL.md file, you record yourself doing the task while talking through your reasoning. Claude captures your screen activity, mouse clicks, keystrokes, and voice narration, then processes all of it into a structured, reusable skill saved to your library. (Claude Help Center: How to create custom skills)
The feature was announced on July 21, 2026, via Claude's official X account. (Claude on X, July 21, 2026)
This matters because written instructions consistently miss the tacit knowledge that makes a workflow work: why you skip a step, which field being empty signals "move on," how you decide what goes first. A live demonstration captures ordering, visual cues, fallback decisions, and small quality-control habits that never make it into a standard operating procedure.
Who Can Use Record a Skill in Claude?
Record a Skill is available exclusively on Claude Pro, Max, and Team plans, inside the Cowork section of the Claude desktop app for Mac. It is not available on the Free tier, not on Enterprise, not on Windows, and not in the web or mobile versions of Claude. (Claude Help Center: How to create custom skills)
The rollout is phased. If you are on a qualifying plan and do not see it, update your Claude desktop app and check again in a day or two.
| Plan | Price | Record a Skill Access | Best For |
|---|---|---|---|
| Free | $0 | No — Cowork is included but not skill recording | Trying Claude |
| Pro | ~$20/month | Yes | Regular daily use, first experiments |
| Max 5x | ~$100/month | Yes | Heavy Cowork usage, multiple skills running daily |
| Max 20x | ~$200/month | Yes | All-day, multi-task operators |
| Team | ~$25/seat/month | Yes | Teams needing seat management + compliance |
| Enterprise | Custom | No | Centralized admin without this feature |
Pricing as of 2026. Check claude.com/pricing for current figures. (Claude pricing)
How to Record Your First Claude Skill: Step by Step
Step 1: Update and open Claude for Mac. This is a desktop-app feature. Make sure you are on the latest version. Browser-based Claude does not have it.
Step 2: Grant macOS permissions. Before recording, Claude needs Accessibility (to track mouse and keyboard) and Screen Recording permissions in macOS System Settings. Restart Claude if it prompts you after granting. (Claude Help Center: How to create custom skills)
Step 3: Clean your screen. Close tabs you do not need, close anything with private details, logins, or client information. The recording captures whatever is visible — not just the parts Claude needs. Anthropic has not published dedicated retention documentation specific to these recordings, so treat it like a screen share with a stranger. Video and audio are not retained after processing, but screenshots from the session are saved and viewable inside the Cowork task. (Claude Help Center: How to create custom skills)
Step 4: Start recording. Open Cowork, click the "+" button in the chat composer, and select "Record a skill." You can also go to Customize > Skills > Add > Record your screen.
Step 5: Perform the task at normal speed. Click the menus, fill in the fields, jump between apps if you need to. Move at your normal working pace — do not rush or deliberately slow down.
Step 6: Narrate the whole way through. This is the part people skip, and it is the most important step. Say what you are doing and why. Say the rules, the exceptions, the things you would tell a new team member on their first day. Claude can already see your clicks — what it cannot see is your reasoning. Your voice is where the judgment lives. Phrases like "I'm opening this file first because everything else depends on what's in here" or "if this field is empty, I skip it and move on" are what turn a recording into a real skill.
Step 7: Stop recording. Click "Done" when finished. There is a ~10-minute time limit — a countdown appears with one minute left, and recording stops automatically at zero. (Claude Help Center: How to create custom skills)
Step 8: Review Claude's proposal. After processing, Claude proposes either a new skill (marked NEW) or an update to an existing skill. Click Content on the proposal card to read the skill before deciding. Click Save to keep it, or Dismiss to discard. Saved skills appear in Customize > Skills. (Claude Help Center: How to create custom skills)
Why Testing Your Recorded Skill Is the Step Almost Everyone Skips
The number-one mistake is recording a task, seeing the skill appear, and assuming it is done. A recording only shows what happened once — with one specific file, one set of data, one path. A useful skill has to generalize: it needs to work on the next example and the one after that, not just the one you demonstrated with.
Test your skill on a fresh example every time. Use a different file, a different input, different data than what you recorded with. If Claude picked up accidental details from your demo instead of the actual rule — for example, if it learned "use the file named Q3-report" instead of "use the most recent quarterly report" — you will only find out when it runs on real work.
Here is how to test properly:
- Trigger the skill with a different input than the one you recorded with.
- Watch what Claude does step by step. Does it follow the underlying rule, or copy the specific details from your demo?
- If it grabs the wrong detail, iterate. Edit the skill description, re-record, or refine the narration.
- Only stop when the skill handles a fresh input correctly.
How Claude Skills Work Under the Hood (Progressive Disclosure)
Understanding how skills load helps you write better descriptions and structure better-recorded demonstrations. Skills use a three-tier loading system called progressive disclosure: (Anthropic Engineering Blog: Equipping agents for the real world with Agent Skills)
| Level | What Loads | When | Token Cost |
|---|---|---|---|
| 1 | Name + description (~100 tokens per skill) | At session startup, for every installed skill | Minimal — enough for Claude to know what exists |
| 2 | Full SKILL.md body | When a task matches the skill's description | Only when relevant |
| 3+ | Bundled files (scripts, references, examples) | Only when the skill body references them | Loaded on demand, not upfront |
This means Claude keeps its context window clear and only pulls in the instructions that apply to the current task. The same skill runs across Claude.ai, Claude Code, and the API — you build it once and it travels. (Claude.com: Teach Claude your way of working using skills) If you are routing Claude into a broader automation stack, this portability is what makes recorded skills a natural fit — see our guide on how to route Claude Opus 5 into your AI agent stack for the bigger picture.
A skill is fundamentally a folder containing a SKILL.md file with YAML frontmatter (a name and description) followed by markdown instructions. When you record a skill, Claude writes this file for you from the demonstration. (Anthropic Engineering Blog)
What Should You Record First? 5 Best Candidates
Not every task is a good first recording. The best candidates share three traits: they are repeated (you do them weekly or daily), visible (they involve screen interaction Claude can capture), and easy to verify (you can tell at a glance whether the result is correct).
- Weekly content or report planning — pulling topics from a source, sorting them into a grid, writing hooks or headers. The narration captures the sorting logic.
- Customer or member onboarding — the welcome sequence, resource checklist, first-call prep. One recording replaces re-typing the process every time.
- Incoming question sorting and labelling — grouping common questions by topic so they become content seeds.
- Report assembly from templates — pulling data from fixed sources into a consistent format with specific ordering rules.
- File organization and cleanup — consistent naming, folder placement, and deletion rules for a recurring file type.
Bad first candidates: long, branching workflows with dozens of exceptions; tasks that involve irreversible, high-stakes actions; anything that would expose passwords or customer records on screen.
Claude Record a Skill vs. Writing a Skill Manually: Which Should You Use?
Before Record a Skill, you had two options for creating a custom skill: write the instruction file yourself, or describe the process to Claude through conversation and let it write the file. Both required you to put the whole workflow into words. (You can still do both — manual skill creation is available on Free, Pro, Max, Team, and Enterprise plans.)
| Approach | How It Works | Who It Is For | Where It Works |
|---|---|---|---|
| Record a Skill | Screen-record yourself doing the task while narrating | People whose tacit knowledge is hard to write down | Mac only, Cowork, Pro/Max/Team |
| Create from conversation | Describe the process to Claude in chat; it drafts the SKILL.md | People who can explain steps but do not want to format them | All platforms, all paid plans |
| Write SKILL.md manually | Author the file directly in a text editor | Developers and technical writers who want full control | All platforms, all plans including Free |
Record a Skill does not replace manual authoring — it adds a third path for workflows that are easier to demonstrate than to describe. Use it when the judgment calls are hard to capture in text. Use manual authoring when the steps are precise and technical. The screen-capture approach behind Record a Skill builds on the same perception-agent technology that makes AI computer use finally reliable in 2026.
Does Record a Skill Suggest Connectors?
Yes. When Claude processes your recording and recognizes that a step in your workflow has an existing connector (an API integration or tool integration available in Cowork), it will suggest using the connector instead of clicking through screens manually. This matters because it means your recorded skill can get smarter over time — Claude points you toward the proper integration when one exists, and only falls back to browsing and clicking when there is no connector. This works with both browser use and computer use inside Cowork.
What This Means for You
If you run a small business, manage repeating operations, or do any task the same way more than once a week, Record a Skill is the fastest path from "I do this manually" to "Claude does this for me." The barrier to entry is effectively zero — no code, no markdown, no file structure knowledge. If you can do the task, you can teach the task.
Start with one small, boring, repeatable job. Record it, narrate the reasoning, test it on a fresh input, and only then decide whether to invest time recording more. The people who get the most value from this feature are not the ones who record the most skills — they are the ones who test each skill on real work before trusting it. If you want to understand the bigger pattern of designing AI agent workflows that run themselves, recorded skills are the building blocks.
For teams, this is how tacit knowledge finally becomes transferable. The person who knows exactly which cells to check before closing the books, the marketer who preps reports the same careful way every week, the ops manager who spots a dodgy supplier invoice in three seconds — recording a skill captures that expertise so it does not leave when they do. If you are building toward a system where Claude handles routine work while you focus on higher-leverage tasks, this fits naturally into a personal AI agent operating system or a self-improving AI agent stack.
For small businesses specifically, recorded skills are the simplest entry point into running operations on AI agents — you start by automating the one task you do the same way every week, and expand from there.
FAQ
Q: What is Record a Skill in Claude Cowork?
A: Record a Skill lets you demonstrate a task on screen, explain your process aloud, and have Claude turn that demonstration into a reusable Skill it can run again without further prompting. It lives under the "+" menu in the Claude desktop app's Cowork workspace.
Q: Which Claude plans include Record a Skill?
A: Claude Pro ($20/month), Max 5x ($100/month), Max 20x (~$200/month), and Team plans. It is not available on Free or Enterprise plans. Check claude.com/pricing for current figures.
Q: Is Record a Skill available on Windows or mobile?
A: No. As of July 2026, Record a Skill is available only inside Cowork in Claude for Mac. It is not in the web browser, mobile apps, or Windows. Manual skill creation (writing a SKILL.md file) works on all platforms.
Q: Does Record a Skill train a new Claude model?
A: No. It creates a reusable, task-specific instruction package — a SKILL.md file — that Claude loads when the task context matches. No model weights are changed.
Q: Can I edit a skill after recording it?
A: Yes. After Claude proposes the skill, you can expand the Content panel to read it before saving. Once saved, you can edit skill files directly beside the conversation in Claude Code or through the Customize > Skills interface. You can also re-record the workflow when the process changes and let Claude update the existing skill.
Q: What happens to the screen recordings — does Claude store them?
A: Video and audio are not retained after processing. A set of screenshots from the session is saved and viewable inside the Recorded demonstration step. Deleting the Cowork task removes the screenshots. (Claude Help Center)
Q: Do skills created by recording work on Claude Code and the API too?
A: Yes. Skills are portable across Claude.ai, Claude Code, and the API. The same skill runs everywhere — you build it once and it travels. (Claude.com: Skills overview)
Q: What is the biggest mistake people make with Record a Skill?
A: Not testing the skill on a fresh example. A recording only shows what happened once. If Claude picks up accidental details from your demo instead of the actual rule, you will only find out when it runs on real work. Always test on different input than what you recorded with.
Discussion
0 comments