No API? Record Yourself Once, Let Claude Take Over

You've done it a thousand times. You've never once written it down.

You Are the Bottleneck, and You Never Noticed

Dana runs a four-person bookkeeping practice out of a strip-mall office in Austin, Texas. Every month, for every client, she logs into her state's sales-tax filing portal and does the same forty clicks in the same order. Pull the numbers. Match them to the right account code. Flag the two exceptions that always come up. File. Confirm.

She has done this so many times she doesn't think about it anymore. Her hands know where to click before her eyes catch up.

That is exactly the problem.

Every new hire who joins Dana's practice has to shadow her for two weeks before they can file a return without supervision. Not because the task is hard. Because nobody ever wrote it down. The portal has no API. It was built before anyone at that state revenue office had heard the word. So the knowledge lives in Dana's hands, and nowhere else.

This is true of almost every small business, in almost every country. The task that eats the most hours is rarely the one on a shiny new platform with clean integrations. It's the ancient booking system. The insurer's portal. The supplier ordering tool your industry has used since 2004. Nobody ever built a plug for it, because building that plug was never worth anyone's time.

Until this week, that meant one thing: you were the plug. If you left, got sick, or forgot a step, the task stalled.

What Anthropic Just Shipped, and Why It's Different

On 21 July 2026, Anthropic added a feature to Claude Cowork, the desktop version of Claude built for running whole workflows rather than just chatting, called Record a Skill. The idea in one sentence: do the task once, on camera, talking through it as you go, and Claude turns the recording into a skill it can run again on its own.

No API. No MCP connector. No developer. If you can click it on a screen, you can teach it. That single change opens up the huge, boring category of software every small business is quietly stuck with: the booking tool, the old CRM, the supplier portal, the government filing site.

That's a big number, but the specific kind of number matters more: bookmarks. People weren't just liking the post. They were saving it to come back to, which is what happens when a feature answers a problem they've been quietly carrying for years.

By 23 July, two days after launch, the AI commentator Miles Deutscher, who has 674,000 followers, was calling it "the best new feature Claude has launched in 2026" and posting his own recorded workflow as proof. "You should be creating a skill library for every single thing you do," he wrote. Within 48 hours, dozens of independent tutorial videos had gone up, walking through the same feature from a dozen angles. If you want the mechanics of how Claude turns a description into a skill without any recording at all, we covered that here; Record a Skill is the demonstration-based sibling of that same idea.

How Do I Automate a Task in Software That Doesn't Have an API?

Ask that exact question and most answers point you toward a developer's toolbox: Robotic Process Automation platforms such as UiPath, code libraries like Playwright paired with a vision model, or specialist browser agents such as Skyvern. All of them work. None of them are something a four-person bookkeeping practice, a dental clinic, or a family logistics firm can pick up on a Tuesday afternoon.

Record a Skill is the answer for the other 99% of businesses. You don't write a script. You don't map buttons or hunt for CSS selectors. You do the job the way you already do it, and narrate the decisions you make along the way, the same way you'd train a new hire standing behind you.

Isn't This Just a Screen Recorder With Extra Steps?

No, and the difference is the narration.

A screen recorder captures what you clicked. It has no idea why. Record a Skill listens while you explain the judgment calls: skip this step if the status is already "live," pick the most recent entry unless told otherwise, ignore that field, it's left over from an old process.

In a live demo of the feature, the creator Simon Scrapes recorded himself setting up an Instagram lead-magnet automation inside ManyChat, a tool with no API at all, that pulls data from a Notion table and posts into a browser-only dashboard. The recording ran 240 seconds and captured 61 steps. Claude then came back with three follow-up questions before saving the skill, questions that caught two things the presenter himself had gotten wrong while narrating. It wasn't just copying clicks. It was checking its own understanding against what actually made sense, the way a sharp new hire would ask, "wait, why did you skip that bit?"

Once saved, the skill ran again on a brand-new case using a companion feature called Claude in Chrome, which takes screenshots, decides what to click, and executes the full 61-step sequence with no one at the keyboard. It picked the right record from Notion, typed the correct keyword into ManyChat, and set the automation live, on its own.

How to Record Your First Skill

1. Pick one task you keep re-explaining. Not the biggest task on your list. The one you've trained the most new people to do, or the one you dread doing yourself every single week.
2. Open Claude Cowork's "+" menu and choose Record a Skill. As of this launch it's available on Mac, on Pro, Max, and Team plans; Anthropic hasn't confirmed a Windows date yet.
3. Do the task exactly as you normally would, out loud. Narrate the "if this, then that" calls you make without thinking. Those verbal asides are what the finished skill will actually rely on.
4. Answer Claude's follow-up questions honestly. If it flags something you did that looks like a mistake, it probably is. Say so, and correct it there.
5. Test the skill on a different, real case before you trust it. Not the same case again. A new client, a new date, a new keyword. Watch it run end to end.
6. Turn it into a scheduled or on-demand task. A skill you have to remember to ask for still depends on you. One that runs on a schedule, or the moment a new record shows up, doesn't.

Recording a Skill vs. Training Your Third New Hire This Year

We've written before about the risk of installing a skill you don't understand; the same caution applies here in reverse. Read the recorded skill back before you trust it with a client's data, the same way you'd read a new employee's notes before letting them file alone.

What Six Months of This Looks Like

This week: one task, recorded, tested, saved.

This month: the two or three tasks every new hire dreads learning, each one a skill instead of a binder nobody reads.

Six months from now: a small library of skills that outlasts any one employee, quietly running the parts of the business that used to depend on one person's memory.

Same clunky old portal. Same forty clicks. A completely different machine behind it.