So a fresh Claude feature just dropped, and the second step is the part that flips everything. You hit record, do a task the way you normally would, and Claude watches. Then this creator, a sharp AI walkthrough guy on YouTube, showed off Claude’s new “Record a Skill” option and taught it to file his expense reports without typing a single prompt. I was genuinely surprised when I saw it work, because it means Claude learns your way of doing things, not its own guess.
Let me break down what he found, because it’s more practical than it sounds at first.
What’s actually new here
Up until now, Claude skills were written instructions. You’d type out how you like a task done, save it, and Claude would pull that skill in when needed. Useful, but you had to describe everything in words.
The new move is screen recording. The author explained that you click around, do the task, and talk out loud like you’re training a new hire. Claude records your screen and your voice, then turns the whole thing into a reusable skill. No prompt writing required.
He pointed out where it’s hidden, since it’s not obvious yet:
- Go to Customize, then Skills on the left, then Add.
- Or start a new chat, open Co-work, hit the plus sign, and record a skill right there.
One catch worth knowing: he mentioned this feature needs a Pro, Max, or Teams plan right now. So free users can’t record yet.
The twist that makes it click
Here’s the part I think matters most. The creator stressed that a recorded skill copies your judgment, not just your clicks. Regular Claude might make its own decisions about how to sort or format something. A recorded skill watches you decide, so it repeats your logic.
That’s the real unlock. You’re not describing a process anymore. You’re demonstrating it, and Claude captures the reasoning you say out loud along the way.
The three demos he ran
The expert tested it on three tasks, from clean to messy.
- Expense report from receipts: He opened a blank Excel report, then went through receipt PDFs one at a time. As he copied each field, he narrated it: pull the date, grab the vendor name, copy the amount, and set the category. He even taught the rule out loud, saying if “software” shows up in the name or description, tag it as software. That single recording took 65 steps, and Claude spun it into a skill.
- Weekly numbers report: He worked from a CSV of made up traffic and signup numbers plus a template his “boss” wanted filled in a set format. He talked through totaling the revenue column, summing new signups, adding up unique website visitors, and dropping each total into the right box. He also told Claude to leave a note for anything that didn’t add up. Nice touch for catching errors.
- Full new client setup: The messiest one. He showed Claude how to create a new client folder, copy a template from a master folder, rename it a specific way, fill it out, and even draft a welcome email. He rushed this one on purpose, spending maybe 30 seconds, just to see how it held up.
The mini-workflow to build your own
Pulling from what the author demonstrated, here’s the flow 🎬
- Set up first: Empty the target folder, line up your files, and open a blank template before you press record.
- Close everything else: He warned that Claude records your full screen, so private tabs are a privacy risk and open windows can confuse it. Minimize it all.
- Record and narrate: Do the task normally, but talk through every decision like you’re teaching a person.
- Let Claude write the skill: It takes a few minutes to generate a skill.md file with the steps it learned.
- Run it: Use the slash command to force the skill, or pair it with a Co-work project folder so it keeps building in the same place.
The honest results
I appreciated that the creator didn’t oversell it. The expense report had a couple of misses. One receipt had no total, and since he never trained that scenario, Claude stumbled on it. His weekly numbers demo went well, and Claude even ignored unrelated files sitting in the same folder. The client setup, despite the rushed 30 second training, nailed the folder, the renamed template, and the welcome email.
His takeaway was clear: one demo isn’t enough. He said you should walk through several examples, including the weird edge cases, so Claude learns how to handle a vendor with an odd name or a receipt missing a field. And skills stay editable. You go back and fix them over time, exactly like coaching a new employee who makes a mistake, then improves on the next round.
Pro tips worth stealing
- 📁 Combine a recorded skill with a Co-work project folder so it becomes a task you keep returning to week after week.
- 🎙️ Narrate your rules, not just your actions. Saying “if it mentions software, it’s the software category” is what teaches the logic.
- ✏️ Treat the skill.md file as living. Open it, review the steps, and update it when Claude gets something wrong.
- ⚠️ Still keep a human review step. It’s strong, but numbers-heavy tasks especially need a quick check.
The person who shared this also put together a free resource with 12 of his favorite skills, including the prompts and finished skill.md files, so you can copy them or customize your own.
Watch the full video to see all three demos run start to finish and get the layout of the skill file 🚀