101s
Share:
Copy link
Copied!
Record it once, run it every month
You've explained the monthly budget v actuals process four times this year. Once to a new analyst. Once to Claude, in a chat, from scratch. Twice to yourself, reconstructing what you did last quarter because you forgot to write it down. Record a skill exists so you do that explaining once, and then never again.
What you're recording
Record a skill is a Cowork feature: you turn on screen recording, perform a workflow the way you normally would, narrate your reasoning as you go, and Claude turns the whole demonstration, the clicks, the typing, the spoken logic, your logins, your websites, and your apps, into a reusable Skill. You can review it, save it, and invoke it on a later cycle (ex: on the 15th of each month).
Where it fits
A skill is useful when the work is repeatable, rules-driven, and runs through a browser or desktop rather than a clean API. Here's a few examples I use
Finance workflow | What you'd demonstrate | What Claude reuses |
|---|---|---|
Actuals vs. budget | Export actuals, open the model, reconcile key lines, flag material deltas, draft commentary | The variance sequence and the write-up structure |
KPI reporting | Pull the standard metrics from your dashboards or data warehouse | The collection and reporting routine |
Board-deck refresh | Update the template from the approved model, check headline numbers | A standardized deck-refresh pass |
Forecast-input collection | Navigate source systems, download files, rename and store them | The recurring gather-and-prep routine |
How to record one
The feature lives in Cowork in Claude for Mac, on Pro, Max, and Team plans, with code execution turned on. As of August 2026, Record a Skill is not available in regular chat, not on Windows, not on Free or Enterprise.
Claude makes it incredibly easy. Open Cowork, select "+ → Record a skill," or go to Customize → Skills → Add → Record your screen. Start recording and do the task the way you normally do it. Narrate the logic behind your choices as you go, especially thresholds, definitions, checks, and what you do when something looks wrong. Select Done, and Claude proposes a Skill for you to inspect before it saves.
Before you proceed against live data or working environment: test the saved Skill against a non-sensitive, representative historical period before you point it at a live reporting cycle. I oftentimes find that Claude gets it 80% of the way there in the first pass; you'll need to test, iterate, and inform of Claude close the gap on the other 20%.
How to make it useful
Recording quality is the whole game here. A rushed take produces a Skill that's wrong and requires a heavy lift to course correct (versus starting off on the right foot).
Start narrow: a task that happens at least monthly, runs 20 to 60 minutes, and has a defined "done" state. Use a sanitized or prior-period data set for the first pass, especially if your systems touch customer, compensation, or non-public financial data. Narrate decision rules, not just clicks, metric definitions, and exceptions. Once complete, ask Claude to review and validate all instructions were followed.
Published: