 |
VOOZH | about |
In the video — Ian, who works in marketing ops, runs his weekly metrics review: a detailed doc for the team and a one-slide summary for leadership. A skill he wrote does the gathering, a scheduled task runs it without him, and he steers the narrative on Monday morning.
Follow along to set up
If you haven’t set up Cowork yet, start with Get started in three steps, then Customize Cowork for connectors and skills.
To dive deeper into Claude Cowork, take the full Intro to Claude Cowork course.
The report is the last thing Claude writes in the video. Before that comes the gathering: the same information is scattered across your email, calendar, and project tracker, and every week Claude pulls it together into a rough first draft for you to review and finish in Cowork.
That information gathering process is the same every week, no matter what the report says. So you build it into a prep skill once. The prep skill tells Claude what data to pull, where to find it, and how to lay out the starting draft.
To set it up:
To start now, open Cowork and describe the report you want to prepare — Claude writes the skill as a plain-text file you can open from Customize → Skills to read or change any time:
Now put the prep skill you built in step 1 on a schedule, so it runs on its own and the data is ready when you start.
There are two ways to create it: type /schedule in any task, or open Scheduled in the sidebar and add a new one.
Here’s the prompt to set it up — replace the blanks with your own:
The scheduled task from step 2 already ran the prep: the data is pulled together into a doc in a folder you chose on your desktop, a starting draft is written, and Claude has named a few possible focus areas.
Ask "How did the prep go?" and Claude walks you through what it pulled and what it couldn’t resolve. From there it’s a short back-and-forth to continue building the full report:
From there, you can tell Claude to turn the weekly review into any format you need, or finish the work in your other tools:
Anything that sends or shares waits for your yes.
Claude pulls the numbers, but the call is yours: the focus, what the review says, what goes out. Weighing that is what the AI Fluency framework calls discernment — applying your own judgment to what Claude produced.
Running the review, you made corrections — a number fixed, a table simplified, a section redirected — and each one is something the skill can learn from. The skill is your process written down, so before you close Cowork, ask Claude to fold those corrections back in:
Ask Claude before you close Cowork: "What did we learn this week that should go into the skill for next week?"
Claude reads back through the work you just did, names what you changed and why, and writes it into the skill. Next week the prep already knows your preferences, your format, and your sources — you don’t re-instruct it on the same things.
Because a skill is a plain-text file in a folder, you can share it. Anyone on the team can run the same review and pick up the same improvements.
This workflow fits any recurring report where the prep is the same every cycle:
The setup is the same every time:
When you arrive, the data is there and the candidates are named. The focus call is still yours.
