Module 5 · 5 lessons · 62 min

Skills: Turn Your SOPs Into Executable Playbooks

5Skills: Turn Your SOPs Into Executable PlaybooksModule 5 · OverviewSkills: Turn Your SOPs Into Executable Playbooks
Module 5
Skills: Turn Your SOPs Into Executable Playbooks

Write it once. It runs the same way every time.

Bruno Ashford
Bruno Ashford · Module 501 / 12
Be honest
When did someone last open your SOP document?
Bruno Ashford
Bruno Ashford · Module 502 / 12
What a skill is

An SOP that actually runs

A folder with a SKILL.md file.

  • Name and description at the top
  • Steps, rules and examples below
  • Loads only when the task needs it
  • Or call it with /skill-name
Bruno Ashford · Module 503 / 12
Where skills live

Project or personal

TypeLocationUse for
Project.claude/skills/<name>/SKILL.mdCompany playbooks, shared with team
Personal~/.claude/skills/<name>/SKILL.mdYour own habits, every project
Bruno Ashford · Module 504 / 12
Your first skill

Fifteen minutes, five moves

  1. 1PickYour most repeated task
  2. 2DescribeExplain it like to a new hire
  3. 3GenerateClaude writes the SKILL.md
  4. 4EditRead it like a manager
  5. 5RunWith the slash, then without
Bruno Ashford · Module 505 / 12
Multi-file skills

Examples beat instructions

Show your best work, not a description of it.

  • template.md for structure
  • examples/ for tone and length
  • checklist.md before handover
  • Keep SKILL.md lean
Bruno Ashford · Module 506 / 12
Skills vs. everything else

One job each

ToolJobThink of it as
CLAUDE.mdWhat is always trueThe handbook
SkillHow a task is doneThe playbook
SubagentSeparate, large workA specialist colleague
ConnectorReach other toolsAccess
HookEnforce a ruleA locked door
Bruno Ashford · Module 507 / 12
Illustrative, based on the examples in this module

What a tested skill changes

60 to 10minutes per proposal
3test cases minimum
0red lines broken
Bruno Ashford · Module 508 / 12
Testing

Three inputs, every time

One passing example proves almost nothing.

  • Normal case
  • Difficult case
  • Edge case with missing data
  • /clear between each test
Bruno Ashford · Module 509 / 12
Fixing
Fix the instruction that caused the failure. Then rerun every test.
Bruno Ashford
Bruno Ashford · Module 510 / 12
Your project

Three tested skills

Proposal, complaint reply, weekly report, or your own.

  • Real anonymised examples
  • Nine tests passed
  • Triggers from plain English
  • Visible in /skills
Bruno Ashford · Module 511 / 12
Recap
Your best way of doing things should not depend on who is in the office today.
Bruno Ashford
Bruno Ashford · Module 512 / 12
01 / 12

Use ← → to move. The marker highlights text and the pencil draws on the slide; navigation locks while you annotate. Undo removes the last mark, Esc exits.

Write a process once and have it run the same way every time, by anyone on your team.

Start lesson 5.1
Bruno Ashford Subscribe