Anthropic shipped a small feature on July 21 with an outsized implication: in Claude Cowork, you can now teach Claude a skill by recording your screen. Do a task once — click through it, talk through it as you go — and Claude turns the recording into a skill it can run again. It's in the + menu of the desktop app as "Record a skill," and it's live on Pro, Max, and Team plans.

If you read one line: the input to automation just changed format. For a decade, making software repeat a task meant describing it — first in code, then in a prompt, then in a SKILL.md file. Record a Skill lets you demonstrate it instead. That's the whole story, and it matters most to the people who never wanted to write any of those three things.

What actually shipped#

The mechanics are deliberately unglamorous. You open Cowork, hit Record a skill, and screen-record yourself doing the thing — pulling the numbers, formatting the report, filing it wherever it goes — while narrating what you're doing and why. Claude watches the demonstration and writes it up as an Agent Skill: a reusable, rerunnable unit that lands in your skill library. Next time, you don't repeat the walkthrough — you invoke the skill.

No prompt to engineer. No SKILL.md to author. No API to wire. The friction that used to sit between "I do this every week" and "an agent does this every week" was mostly authoring friction, and this removes it.

Why founders should care more than the feature's size suggests#

If you're a solopreneur or a two-person company, you are the ops team. The tasks that eat your week — assembling the weekly report, prepping a client, reconciling an invoice, onboarding a new user by hand — are exactly the ones that were never worth stopping to automate, because stopping to describe them cost more than just doing them again.

Record a Skill inverts that math. The cost of capturing the automation drops to roughly the cost of doing the task once, on camera. That's the first time the break-even has been low enough for the non-technical operator to bother.

For years, the barrier to automating your own work wasn't the doing — it was having to translate the doing into a language a machine would accept. Demonstration removes the translation step.

There's a second-order effect on Team plans, where recorded skills are shareable across the org. A small company's real operating manual usually doesn't exist — it lives in one founder's head as "how we do invoices" and "how we file the Monday report." A recorded, shareable skill is the first version of that knowledge that's both written down and executable. It's continuity insurance for a company too small to have written anything down.

The caveat that keeps this honest#

Recording removes the authoring friction. It does not remove the reliability work, and it would be a disservice to pretend otherwise.

An Agent Skill fires — or doesn't — based on its name and description, because that metadata is what the model pre-loads to decide when to reach for it. A skill with a perfect recorded body behind a vague description will sit there and never trigger. That's the single most common failure mode of hand-authored skills, and recording doesn't fix it; it just moves the fix to after capture. So treat the recording as a first draft: tighten the description so it names what the skill does and when to use it, and test it against the requests you actually make.

The other limit is determinism. Demonstration captures what you did, not why the numbers were where they were. If a task's steps depend on judgment that changes week to week, a recorded skill will happily replay last week's judgment. The tasks that record cleanly are the ones that are genuinely repeatable — click-driven, rule-following, boring in the good way.

The through-line#

Put this next to the rest of Anthropic's Cowork push — an office agent that now runs on your phone, async, while your laptop is closed — and the strategy reads clearly: the company is building for the majority of its users who don't code. Record a Skill is the on-ramp for that majority. It's the answer to "I'd automate this, but I don't know how to tell it what to do." Now you don't tell it. You show it.

For a founder, the move this week is small and concrete: pick the one recurring task you resent most, record yourself doing it once, and see what comes back. Worst case, you've written the first line of your operating manual. Best case, you never do that task by hand again.