One Agent, a Stack of Playbooks: Turn Your Repeat Tasks Into Claude Skills

promptI want to turn the work I repeat into Claude Code skills. Interview me about my job using the AskUserQuestion tool.

Go one topic at a time:
- My role, who I do the work for, and what a normal week looks like.
- Every task I do more than once a month: what kicks it off, what I start with, the steps, the tools and files I use, and what "done" looks like.
- Where each task goes wrong, the judgment calls I make, and the rules I never break.
- Where my best past examples of each task live, so you can learn from them.

Don't ask obvious questions. Dig into the steps I do on autopilot and would forget to mention.

When we've covered everything, write PLAYBOOKS.md with a table: task, how often, time per run, trigger, inputs, output, and whether it's a good skill candidate (repeatable steps and a clear finish line). Rank the candidates by hours saved per month. Don't build anything yet.

promptTake the top task in PLAYBOOKS.md and turn it into a Claude Code skill.

1. Pick a short kebab-case name I'd actually type, like weekly-report.
2. Create ~/.claude/skills/<name>/SKILL.md with these sections: frontmatter (name, description), When to use, Inputs, Steps, Rules, Done when, Output.
3. Start the description with what the skill does, then the exact phrases I'd use to ask for it.
4. Write the steps as numbered instructions with my real tools, folders and rules from the interview. No generic advice.
5. Keep SKILL.md under 500 lines. Put long reference material, examples or templates in separate files in the same folder and link to them from SKILL.md.
6. If the task has side effects (sends, posts, deletes, deploys or spends money), add disable-model-invocation: true so it only runs when I type the slash command.
7. Show me the file before you save it. Then run it on one real example and fix whatever went wrong.

markdown---
name: task-name
description: What this does in one line. Use when I say "...", "...", or ask you to ....
---

# Task name

## When to use
- Trigger: what kicks this task off
- Not for: similar jobs this skill should not handle

## Inputs
- What I give you: ...
- Where to find the rest: folders, files, links

## Steps
1. ...
2. ...
3. ...

## Rules
- What must always be true
- What you must never do

## Done when
- A finish line you can check (file saved at ..., every row filled, totals match the source)

## Output
- Format, length, where to save it, and who it is for

markdown---
name: client-update
description: Drafts the weekly client update email from this week's project notes. Use when I say "client update", "weekly update", or "write the Friday email" for a client.
---

# Client update

## When to use
- Trigger: end of the week, or when I ask for a client update
- Not for: invoices or proposals

## Inputs
- The client name. Ask if I didn't give one.
- notes/<client>/ for this week's notes

## Steps
1. Read every file in notes/<client>/ changed in the last 7 days.
2. List what shipped, what is in progress, and what is blocked, with dates.
3. Draft the email in 3 short sections: Done, Next, Need from you.
4. Take every number and date from the notes. Never estimate.

## Rules
- Plain language. No jargon, no hype.
- If something slipped, say so in the first section with the new date.
- Draft only. Never send anything.

## Done when
- Every item traces back to a note file.
- The email is under 200 words.

## Output
- Save to drafts/<client>-update-<date>.md and show it to me.

promptThat run of /client-update had problems. Update ~/.claude/skills/client-update/SKILL.md so the next run gets it right:
- Add a step or rule for each mistake you made this session.
- Keep what worked.
- Show me the diff before you save it.