Claude Cowork Can Build Skills by Watching You
Anthropic just shipped a feature that lets you record yourself to create skills in Claude Cowork: it watches your screen, listens to you explain, and writes the skill for you. In this walkthrough I teach it how I engage with my YouTube comments, then show you exactly when recording is the right choice and when you should build the skill by talking instead.
What you need
- Claude Cowork in the Claude desktop application, with the new Record a Skill option in the plus menu
- A microphone, so you can narrate what you are doing while you record
- A workflow you repeat often enough to be worth teaching
1. Claude Cowork's Record a Skill feature (0:00)
The way you use it is very simple. Click the plus arrow in Cowork and you will see the new option, Record a Skill. Click it and Claude triggers a recording session where it not only records your screen but also listens to you speak into your microphone. That combination, actions plus narration, is what it learns from.
2. Recording a skill step by step (0:24)
For the demo, I open the comment section of my previous video. I like a comment, heart it, read it, then move to a shorter one and reply out loud: the commenter uses Gemini 3.5 Flash Lite for dictation, and I agree, that model is probably my favorite one. I am showing Cowork how I actually reply to the comments on my YouTube videos.
When I am happy, the recorder has logged sixty-eight steps in a fifty-second recording. I click Done and it analyzes the whole session, including everything I said out loud. It takes screenshots every single time you click or scroll, which is exactly why you want to be very precise with your movements. Then it builds the skill, which takes a couple of seconds.
3. Is recording actually more efficient? (1:55)
Here is the real question: is this a more efficient way of building skills than just iterating with Claude Cowork in chat? The answer is, it depends. The fundamental question you have to ask yourself before building any skill is: can I plug Claude directly into this application?
4. The connection test: MCP, API, or CLI (2:15)
If you can connect, there are three types of connections available to your Claude account:
- MCPs: anything you see in the Connectors tab of your Claude application. This is the standard way to connect your account to other services.
- APIs: a bit more complex, but Claude Code can walk you through getting API access for most services.
- CLIs: for the most advanced users. If you have never used a CLI, do not worry, you do not need to; MCPs and APIs are completely fine.
If any of these three methods works for your application, build the skill by talking. It is a lot more efficient. For example, there are services that connect Claude straight to YouTube: the YouTube API gives you the comments, and there are free resources that do exactly the same thing.
5. When recording is the right choice (3:36)
The second scenario is where this feature is excellent: when you cannot connect to the application by any means other than logging yourself in. That is browser use automation, and the problem with browser use is that it is very slow. Extremely slow. Use it as a last resort, really.
Where does that happen? Applications that do not offer a connection, or whose connection is very expensive. Think many social media platforms, and legacy software like accounting tools or ERPs. That is where you want to get very detailed with recording yourself actually doing the work.
6. Reviewing the generated skill (4:29)
Back in Cowork, Claude tells me what it saw: it recorded how I engage with comments on my own YouTube videos, like, heart, and reply in my voice. After I confirm, it creates the skill: YouTube Comment Engagement, described as engaging with the comment section of the user's own YouTube video. I give it a URL, it goes into the video, reads the comments, likes them.
What is cool is that it found the actions associated with each button. The old problem with browser automation was that you could never show the AI what you meant, so it clicked all over the place unless your prompts were extremely detailed. Now you film yourself for five to ten minutes and Claude works it out. I could save the skill from here, but I left it out for the demo.
7. The one rule to remember (5:46)
Before using this feature, ask the one fundamental question: can I connect to this application via a simple method? You can even ask Claude to do the connections for you. If you can connect, create the skill by talking with Claude; that is what connections were built for. If you cannot, take five to ten minutes and film yourself building the skill.
One more thing worth knowing: a skill built in Cowork is not locked to Cowork. It can also be used by Claude Code or any other application with access to the browser.
Final takeaways (6:36)
Recording is not a replacement for connections, it is the fallback for when connections do not exist. Get that decision right and this feature becomes genuinely useful instead of a slower way to do what an API does better.
Pitfalls and tips
- The recorder screenshots every click and scroll, so keep your movements deliberate and clean; sloppy recordings produce sloppy skills.
- Do not record a workflow that has an MCP, API, or CLI available. Talking is faster and the connection will always beat the browser.
- Browser automation is the slowest path there is. Reserve recorded skills for apps that truly have no other way in.
Where to go next
- Understand the sandbox this all runs in with Claude Cowork vs Claude Code: What's the Difference?.
- Put your skills to work at scale with Claude Fable 5 Is Here to Stay - Maximize Your Usage.
