Playbooks: copy what already works
Twelve playbooks, all following the same shape:
At a glance → the situation → preparation → the prompt → why it is written that way → acceptance checklist → variations → FAQ
Every prompt sits in a text block so you can copy it whole. Swap the filenames, paths and field names for your own and it runs.
Where to start
Pick whatever you most want to stop doing by hand:
| # | Playbook | Uses | Difficulty |
|---|---|---|---|
| 01 | Bulk rename and file triage | Local file operations, preview-then-confirm | Beginner |
| 02 | Recording to minutes to to-dos | Local Whisper, structured output | Beginner |
| 03 | One sentence to Word and PPT | Office document suite, experts | Beginner |
| 04 | Spreadsheet to visual report | xlsx Skill, chart generation | Beginner |
| 05 | A daily briefing that sends itself | Connectors plus automation | Intermediate |
| 06 | Social posts and video scripts | Role setting, iteration | Beginner |
| 07 | A local app with no code | Code development mode | Intermediate |
| 08 | Turn a routine into a Skill | Creating Skills | Intermediate |
| 09 | Run Tencent Meeting by sentence | Tencent Meeting Skill | Intermediate |
| 10 | Run Tencent Docs by sentence | Tencent Docs connector | Intermediate |
| 11 | Command your PC from the train | Assistant | Intermediate |
| 12 | Web research and competitor intel | Web Search, Agent Browser | Intermediate |
Four rules that apply throughout
These hold for every playbook, so they are stated once here rather than repeated.
One: work on copies
For anything that modifies files (01, 07 and 08 especially), copy it into a separate folder first and let it work there.
Automatic backup is a safety net, not a licence.
Two: ask for a preview, then execute
For any bulk operation, deletion or overwrite, the first round produces a list, not an action.
The standard phrasing:
Show me a preview first and execute only after I confirm. Present the preview
as a comparison table. Do not modify any file yet.Three: state the output format and location
"Tidy this up" gets you a block of chat text. "Output as a Markdown file saved to the workspace, named xxx.md" gets you a file you can open.
The second is what you wanted.
Four: check for invented content first
The first acceptance test for all AI output: did it turn something absent into something present?
Watch these fields especially — owners, dates, figures, cited sources. Where the source material does not say, the correct behaviour is to leave it blank or write "not specified", not to fill in something plausible.
If it invented something, reply: For fields with no clear basis, write "not specified" — do not infer.
Beyond the playbooks
A playbook gives you a pattern, not a final answer. Getting real leverage from WorkBuddy takes two more things:
- Freeze what worked → Turn a routine into a Skill
- Hand over the recurring parts → Automations on a schedule
Reusable prompts are collected in the Prompt library.