Claude watches you work now

The second step is the one that flips everything

August 08, 2026

In partnership with

You hit record. You do the task the way you always do it. Claude watches.

That is it, and I sat up when I saw it run. I found the walkthrough from a YouTube creator who teaches this stuff carefully, and he taught Claude to file his expense reports without typing a single prompt.

What got me is not the automation. It is that Claude ends up learning my way of doing the task rather than its own guess at how it should be done.

Your prompts are leaving out 80% of what you're thinking.

When you type a prompt, you summarize. When you speak one, you explain. Wispr Flow captures your full reasoning — constraints, edge cases, examples, tone — and turns it into clean, structured text you paste into ChatGPT, Claude, or any AI tool. The difference shows up immediately. More context in, fewer follow-ups out.

89% of messages sent with zero edits. Used by teams at OpenAI, Vercel, and Clay. Try Wispr Flow free — works on Mac, Windows, and iPhone.

*Ad

Until now, a skill was something you had to describe

Claude skills were written instructions. You typed out how you like a task handled, saved it, and Claude pulled that skill in when it was relevant.

Useful, genuinely. But everything had to survive the trip through my words first, and describing a process in prose is a lossy way to hand it over.

The new option is screen recording. You click around, do the task, and talk out loud like you are training a new hire. Claude records your screen and your voice, then turns the whole session into a reusable skill.

It is tucked away, so here is where to find it

Go to Customize, then Skills on the left, then Add.

Alternatively, start a new chat, open Co-work, hit the plus sign, and record a skill from there.

One catch worth knowing before you go hunting: the creator noted this needs a Pro, Max, or Teams plan right now, so free accounts cannot record yet.

The twist that makes it more than a macro

This is the part I keep coming back to. A recorded skill copies your judgment, not just your clicks.

Regular Claude will make its own decisions about how to sort or format something, and its decisions are reasonable in general and wrong for you specifically. A recorded skill watches you decide, so it repeats your logic instead.

You are not describing a process anymore. You are demonstrating one, and the reasoning you say out loud gets captured along with the actions.

How Jennifer Aniston’s LolaVie brand grew sales 40% with CTV ads

The DTC beauty category is crowded. To break through, Jennifer Aniston’s brand LolaVie, worked with Roku Ads Manager to easily set up, test, and optimize CTV ad creatives. The campaign helped drive a big lift in sales and customer growth, helping LolaVie break through in the crowded beauty category.

*Ad

He tested it on three tasks, from clean to messy

The expense report came first. He opened a blank Excel report and worked through receipt PDFs one at a time, narrating as he copied each field: pull the date, grab the vendor name, copy the amount, set the category. He also taught a rule out loud, saying that if "software" appears in the name or description, it gets tagged as software. That single recording ran sixty five steps, and Claude turned it into a skill.

The weekly numbers report came second. He worked from a CSV of invented traffic and signup numbers plus a template his hypothetical boss wanted filled in a fixed format. He talked through totaling the revenue column, summing new signups, adding up unique visitors, and dropping each total into its box. He also told Claude to leave a note beside anything that did not add up, which strikes me as the smartest thing he did in the whole video.

The full client setup was the messy one. He showed Claude how to create a new client folder, copy a template out of a master folder, rename it a specific way, fill it out, and draft a welcome email. He rushed this one on purpose, spending maybe thirty seconds, just to see how it held up under sloppy training.

The setup matters more than the recording

Prepare before you press record. Empty the target folder, line up your files, and open a blank template first, because the recording captures whatever mess is already on screen.

Close everything else. Claude records your full screen, so private tabs are a real privacy exposure and stray windows can confuse the result. Minimize all of it.

Record and narrate. Do the task normally, but talk through every decision as though a person were sitting next to you learning it.

Then let Claude write the skill. It takes a few minutes to generate a skill.md file with the steps it learned from you.

Then run it. Use the slash command to force the skill, or pair it with a Co-work project folder so the work keeps accumulating in one place.

The GTM Playbook Behind Warmly's Acquisition

Warmly ran pipeline, outreach, and lead scoring on autopilot for hundreds of startups — before a single sales hire.

HubSpot acquired them for it. Now the cofounders are walking you through the exact system, live, before they disappear into product. Join the Builder Session on August 12.

Leave with an agentic GTM stack you can replicate this week. Plus HubSpot Credits when you join HubSpot for Startups.

*Ad

The results were honest, which is why I trust them

The expense report had misses. One receipt had no total on it, and because he never trained that scenario, Claude stumbled there.

The weekly numbers demo went well, and Claude correctly ignored unrelated files sitting in the same folder. The client setup, despite the deliberately rushed thirty second training, got the folder, the renamed template, and the welcome email right.

His conclusion is the part worth keeping. One demo is not enough. You walk through several examples, including the weird edge cases, so Claude learns what to do with a vendor with an odd name or a receipt missing a field.

Skills stay editable, which changes how you should treat them

The skill.md file is not a finished artifact. You open it, read the steps Claude wrote, and fix what it misunderstood.

That is coaching a new employee who makes a mistake and does better on the next round, and it is a far more forgiving model than getting a prompt perfect on the first try.

A few things worth stealing from his setup. Narrate your rules and not only your actions, because saying "if it mentions software, it is the software category" is what teaches the logic rather than the motion. Pair a recorded skill with a Co-work project folder so it becomes a task you return to weekly. Keep a human review step, especially on anything numbers heavy.

What I am recording first

The tasks I have never automated are not the complicated ones. They are the ones I could never explain properly. Filing, renaming, categorizing, the small judgment calls I make without noticing I am making them.

Those are exactly the tasks that describing in a prompt destroys and demonstrating preserves. That is the shift here, and it is bigger than a new menu item.

So pick the chore you do every week and could not write instructions for if someone asked. Clear the folder, open the template, and record yourself doing it once tonight while saying every decision out loud. Then read the skill.md it writes and see how much of your own logic came back.