Introduction
You know that task you do every single week and keep meaning to automate, but never do? Claude can now learn it by watching you do it once. The feature is called “Claude Record a Skill,” and it turns a simple screen recording of your workflow into a reusable Skill that Claude can run again on command. No prompt engineering. No code. You just do the job while narrating what you’re doing, and Claude writes the automation for you.
Anthropic rolled this out on July 21, 2026, inside Claude Cowork on Mac, for Pro, Max, and Team plans. For anyone running a lean e-commerce or print-on-demand operation, it’s the closest thing yet to cloning your own busywork. Here’s how it works, where it earns its keep, and the one thing it still can’t do for you.
What “Claude Record a Skill” Actually Is
A Claude Skill is a reusable set of instructions that teaches Claude how you want a specific task done. Until mid-2026, building one meant writing a structured file by hand.
Record a skill flips that. Instead of writing instructions, you show them. Claude captures your screen, your clicks, and your voice, then turns the whole demonstration into a Skill you can trigger later. Think of it as training a new hire who shadows you once and never forgets.
It lives in Claude Cowork, Anthropic’s workspace that can read files, browse the web, and run tasks for you. Once a Skill is saved, you can run it in a fresh chat, edit it, share it with your team, or even schedule it to run on its own.
How to Record a Skill, Step by Step
The flow is genuinely simple once permissions are set:
- Set up. Update Claude for Mac. The first time, grant the Accessibility and Screen Recording permissions macOS asks for. Close anything you don’t want on camera.
- Start recording. In Cowork, hit the “+” button and pick “Record a skill.” Keep your mic on.
- Do the task for real. Run through the workflow exactly as you normally would. Recordings last about 10 minutes, with a warning before time’s up.
- Say the quiet part out loud. Narrate why you do each step: why you skip a row, how you choose between options, what to do when something’s missing. Claude captures every click, so stay on task.
- Review and save. Click “Done.” Claude reviews the recording and drafts a new Skill (or suggests updating an existing one). Read it, then save.
- Reuse it forever. Your Skill shows up in your library. Call it up in a new chat, or ask Claude to turn it into a scheduled task that runs, say, every weekday morning.
One note on privacy: Anthropic says the video and audio aren’t kept, only screenshots from the session. Still, don’t type passwords or show client data while recording.
Where This Pays Off for E-Commerce Teams
Most of the work that clogs an operator’s week isn’t creative. It’s repetitive. Anthropic’s own data backs this up: across a large sample of Cowork sessions, more than 90% of usage was non-coding work, and “business process and operations” was the single biggest category. That’s exactly the stuff worth recording:
- Product listings. The path from spec sheet to SEO title to on-brand description to a Shopify draft, recorded once with your rules narrated.
- Weekly reporting. Pull the same numbers from the same dashboards and format them the same way, every time.
- Data cleanup. Renaming files, reformatting exports, tidying POD image batches to your conventions.
- Content repurposing. Splitting a blog post into platform-specific versions and scheduling them, on a daily loop.
- Onboarding. Capture how your most experienced person handles a workflow, exceptions and all, and hand it to the next hire.
The payoff isn’t hypothetical. Research from the Federal Reserve Bank of St. Louis found that workers who use generative AI save about 5.4% of their work hours, roughly 2.2 hours a week, and the biggest savings go to people using it daily, which a saved Skill makes easy. It fits right into the kind of AI content workflows smart teams use to scale output without adding headcount.
Recorded Skill vs. Writing One By Hand
Both get you a working Skill. They just suit different jobs.
| Record a skill | Writing a skill by hand | |
| How you build it | Screen-record and narrate a demo | Write the instructions and metadata yourself |
| Skill needed | None, fully non-technical | Comfort with files and formatting |
| Best for | Mechanical, click-path tasks | Complex or judgment-heavy tasks |
| Availability | Pro/Max/Team, Cowork on Mac | Free through Enterprise, plus API |
| Speed to first skill | Minutes | Longer to author and test |
For 80% of daily grind work, recording is faster and friendlier. For anything intricate, hand-writing still gives you more control.
The One Thing It Can’t Record
Here’s the honest limitation. A recording captures what you did, not always why. As one operator who’s built dozens of Skills by hand put it, the real skill is everything you did on purpose. Rush through a silent demo and you get a Skill that mimics motions without understanding them. Narrate well, and it captures your reasoning.
And some work simply doesn’t come off a screen. A camera can record the steps to export a design, but not the taste that decides whether the design is any good. Brand voice, visual judgment, whether a layout actually converts. That’s human work, and it stays human. This is the split serious brands lean into: automate the repeatable, and keep experienced designers on the creative calls. It’s the whole idea behind a design subscription model, where the mechanical work gets systemized so the creative work gets real attention.
Conclusion
Claude record a skill is a small feature with a big implication. The busywork you’ve been meaning to automate for months can now be captured in a single ten-minute recording. Start with one boring, low-risk task, narrate it like you’re training someone, and test it before you trust it. Build a few solid Skills and the hours add up fast.
Just remember what to keep on your own plate: the design and brand decisions that make customers actually buy. If that creative side is the piece slowing you down, see how Design Musketeer’s plans work and pair your new automation habit with a team that owns the work a recording never could.
FAQ
What plans support Claude record a skill?
It’s available on Pro, Max, and Team plans, inside Claude Cowork on Claude for Mac. It isn’t in regular chat, on Windows, or on Free plans as of launch.
Do I need to know how to code?
No. That’s the entire point. Claude writes the Skill from your demonstration, so you never touch a line of code or a config file.
Does Claude keep my screen recording?
Anthropic says the video and audio aren’t retained. Only screenshots from the session are saved with the task, and deleting the task removes them. Still, keep passwords and private data off-screen.
How long can a recording be?
About 10 minutes, with a countdown warning before it stops automatically.
How do I run a recorded skill again?
Open it from your Skills library, trigger it in a fresh chat, or ask Claude to turn it into a scheduled task that runs on a set cadence.
What tasks should I record first?
Start with repetitive, procedural work using non-sensitive data, like formatting a weekly report or prepping a product listing. Save judgment-heavy creative work for a human.