There’s a very specific friction point that kills a lot of good automation ideas before they even start: you know exactly how to do a task, but turning that into a written SKILL.md—the steps, the exceptions, the “oh, and if the field comes back empty, do this instead”—takes you more time than just doing the task yourself for the tenth time. Anthropic removed that middle step. Since July 21, 2026, Claude Cowork has an option called Record a Skill: you perform the task on screen, narrate your reasoning out loud, and Claude converts that recording into a reusable Skill. No SKILL.md, no prompt engineering.
Updated August 27, 2026. Anthropic published official documentation for the feature after this post. Two important things change from the original note: the video and audio from the recording are not retained (what does remain are screenshots from the session), and the feature is exclusive to Claude for Mac—it’s not on Windows. The corrected details are below.
What is Claude Cowork?
Before diving into the feature, in case you landed here looking for the basics: Cowork is not a separate product. It’s a capability within Claude that completes end-to-end tasks on your files and tools—instead of returning text in a chat for you to copy and paste, it delivers finished work for you to review.
What platforms does it work on? The desktop app (macOS, Windows, Linux, ChromeOS) has the full experience. Web and mobile are in beta for Pro, Max, and Team plans. The Chrome sidebar is available on Max and Team.
Some things remain exclusive to desktop because they depend on your machine: access to local files, MCP connectors and local servers, browser use, computer use, and live artifacts. Starting and directing tasks, Skills, scheduled tasks, and connectors work across all three surfaces.
Is Claude Cowork free? How much does it cost?
There is no free Cowork plan. Cowork comes included in Claude’s paid plans at no additional cost or separate subscription—what changes between plans is not the access but the usage limit. Claude’s Free plan does not include it.
For Record a Skill specifically, the requirement is stricter: Pro, Max, or Team. It’s not available on Free or Enterprise.
What are Claude Skills?
A Skill is a saved procedure: you teach Claude how to do a specific task once, and then it can repeat it. Technically it’s a folder with a SKILL.md file—YAML frontmatter with required name and description fields, plus instructions—and optionally supporting files or executable scripts in Python or JavaScript for more serious automation.
Record a Skill is simply a way to generate that package without writing it.
The facts, summarized
Record a Skill lives within Cowork and converts an on-screen demonstration into a reusable Skill. What you need to know before trying it:
| Plans | Pro, Max, and Team |
| Platform | Claude for Mac only — not Windows, not web, not mobile, not in chat |
| Requirements | Latest version of the app + macOS permissions for Accessibility and Screen Recording |
| Duration | ~10 minutes per recording |
| What’s retained | Screenshots from the session. The video and audio are not. |
That platform restriction is what surprises most people: Record a Skill is not on Windows, even though Cowork in general is. If you’re on Windows, you have Cowork but not this way of creating Skills.
How do you record a Skill?
- Update Claude for Mac to the latest version and grant Accessibility and Screen Recording permissions in macOS.
- Open Cowork and start recording from the + button in the composer or from Customize → Skills.
- Perform the workflow on screen. A capture bar shows you that recording is active and counts the captured steps.
- Narrate as you work. The microphone is on by default—you can mute it or change input from the microphone control. The narration gives Claude context that the screen doesn’t show: why you’re skipping a step, how you’re choosing between two options.
- When a minute remains, a countdown appears on the capture bar. When it hits zero, recording stops automatically and what was captured is sent to Claude.
- Claude proposes a new Skill or updates to an existing one. Expand Content to review what it generated, and choose Save or Dismiss.
That point 6 is more useful than it sounds: you can record a second pass of a workflow you already had saved and let Claude refine the existing Skill instead of creating a duplicate.
Where it fits among the ways to create a Skill
This isn’t the first way to create a custom Skill—it’s the fifth. Before this, you could: write a SKILL.md by hand; ask Claude to draft one from a written description; complete a workflow in Cowork and ask it to package the successful run as a Skill afterward; or upload an already-built Skill package.
Record a Skill is different because it captures the process as it happens, not from memory afterward—and that matters more than it sounds. People usually leave out small details when documenting a task they know from memory: the visual cue that tells you something’s wrong, the exception you always make for a particular client, the double-check you do without thinking. A live demonstration catches that by default.
What happens to what was recorded?
This was the open question when we published the original note, and it now has an official answer.
The video and audio from the recording are not retained. Claude processes them to build the Skill and they’re not saved. What does persist, within the associated Cowork task, is a set of screenshots from the session.
That’s quite a bit better than the worst-case scenario, but it doesn’t eliminate caution—it just makes it more precise. A screenshot still contains everything that was visible at that moment: account numbers, customer names, internal interfaces, the sidebar tab that had nothing to do with the task. If it’s on screen, it’s in the screenshots, and the screenshots stay.
Practical recommendation, now with better foundation than before: close what isn’t part of the workflow before recording, and do your first pass on a test version before recording something that touches real credentials, customer data, or regulated information. The risk isn’t the video—it’s the frame.
Where this is genuinely useful
The workflows that fit best are ones with fixed and repeatable steps, with little ambiguity: recurring report formatting, standard data entry with consistent fields, upload workflows with fixed metadata, email triage that follows an established process. The ~10-minute limit also pushes in that direction—if your process doesn’t fit in ten minutes, it’s better to split it into smaller Skills and chain them.
Tasks that vary a lot between runs, require real judgment, or touch sensitive data are better handled interactively for now.
Grego’s strategic note: the real change isn’t the recording, it’s who can create automation now
Here’s what I’d pay attention to if I were leading a team. The interesting part of Record a Skill isn’t the screen-recording mechanism itself—screen recorders with AI summaries aren’t new—. It’s that Anthropic just reduced to zero the distance between “the person who knows how to do the task” and “the person who can automate it”. Until now, whoever understood a workflow well enough to do it quickly usually wasn’t the one who could translate it into clear instructions for an agent. That translation step was exactly what got skipped or done poorly, and it’s precisely what this eliminates.That’s real productivity gain. It’s also a governance question that lands squarely in CIO territory. The retention part they’ve already answered—the video doesn’t stay, the screenshots do—. What remains unanswered is the ownership piece: who owns a recorded workflow once it’s captured, what happens to it if the person who recorded it leaves the team, and in Team plans, what are the actual defaults for sharing a Skill built from someone’s screen with the rest of the organization. The Skills documentation describes sharing controls that exist for Skills in general, but doesn’t clarify anything specific for recorded ones—which means the sensible thing is to review your current admin controls directly, instead of assuming the general policy covers this thoroughly.
For regional teams, I’d frame it this way: the efficiency case for this feature is strong and immediate—it’s a genuine “do more with less” tool, not a marketing angle. And now that we know exactly what gets saved, the pilot can be designed properly instead of blindly: low-risk workflows, clean screen, and a review of what ended up in the screenshots before scaling to anything that touches regulated data or customer information.
The takeaway
Record a Skill takes the most tedious part of building automation—writing it—and replaces it with simply doing the task once. That’s a real lowering of the barrier to entry.
Two conditions before you get excited: you need a Mac—it’s not available on Windows—and whatever ends up in your screen captures stays there. Clean up your desk before you hit record.
Would you trust an AI-recorded version of your own workflow to run unsupervised, or is this a “pilot only” feature for now?
Sources:
- How to create custom skills — Anthropic Help Center (official feature documentation)
- Use Claude Cowork on web, desktop, and mobile — Anthropic Help Center
- Claude (@claudeai) on X — official launch announcement, July 21, 2026
- Claude Cowork learns new skills through screen recordings and voice-over explanations — The Decoder
- Anthropic’s Claude Cowork Lets You Teach AI by Recording Your Screen — AlphaSignal