// FREE CHECKLIST

Your first skill in 15 minutes.

The step-by-step checklist that takes you from "what is a skill?" to a working custom automation. No code required.

  • Pre-flight checks so your skill works first time
  • Copy-paste SKILL.md template with annotations
  • Testing workflow that catches errors before they cost you tokens
// CHECKLIST PREVIEW
Pre-flight → Requirements and setup checks
Build → SKILL.md template with annotations
Test → Verification workflow that catches errors

Follow the checklist. Your first skill works on the first try.

No spam. Unsubscribe anytime.

What's Inside 3 Phases
// Phase 1

Pre-flight Checks

Everything you need before you write a single line of your skill.

Setup
// Phase 2

Build the Skill

Annotated SKILL.md template you can copy, paste, and customize.

Template
// Phase 3

Test and Ship

The testing workflow that catches trigger failures and formatting issues.

Verify

Your first skill. No code. 15 minutes.

Enter your email for the complete checklist with copy-paste templates.

No spam. Unsubscribe anytime.

Free Checklist

Cowork Skill Builder Checklist

Everything you need to turn a repeating Cowork task into a reusable skill. Check items off as you go.

0 / 18 complete
1
Should You Build a Skill?
✓
You have given Cowork this type of instruction more than twice
If you are repeating the same context, format, or workflow, it is time to capture it.
✓
The output needs consistent format or quality
Proposals, scripts, reports, emails that need to look and sound the same every time.
✓
There is domain knowledge Cowork does not have by default
Brand voice rules, industry frameworks, pricing models, compliance requirements.
2
Write the SKILL.md
✓
Name field is set (short, lowercase, hyphenated)
Example: youtube-script, client-proposal, weekly-report
✓
Description includes trigger phrases people actually say
Not just what it does, but when to use it. "Use this skill whenever the user says..."
✓
Description uses YAML block scalar (>) if it contains colons
Prevents parsing errors when packaging. Use description: > then indent the text below.
✓
Purpose statement explains what makes this skill different
One paragraph. Not marketing copy. A calibration statement that shapes output quality.
✓
Workflow is written as instructions, not a single prompt
Step-by-step: gather inputs, make decisions, do the work, review. Runs for any variation of the task.
✓
Output format is explicitly defined with a template
Section headers, structure, formatting. Cowork needs to know what the final deliverable looks like.
✓
Anti-pattern checklist catches your known failure modes
"If this, then fix that" pairs. Add one every time Cowork produces something you don't like.
✓
SKILL.md is under 500 lines
If it is longer, split detailed guidance into reference files. Keep the main file lean.
3
Structure the Folder
✓
Skill lives in its own named folder
skill-name/SKILL.md is the required structure. The folder name matches the skill name.
✓
Reference files are in a references/ subfolder
Detailed knowledge that applies to some runs but not all. Cowork reads them on demand.
✓
SKILL.md tells Cowork exactly when to read each reference
"Read references/X.md for detailed Y." Clear pointer with context on when it is needed.
✓
Large reference files (300+ lines) have a table of contents
Helps Cowork find the right section without reading the entire file.
4
Test and Iterate
✓
Ran the skill on a real task (not a test prompt)
Use it for actual work. The output quality tells you what needs fixing better than any test case.
✓
Reviewed the output and added fixes to the anti-pattern list
Every flaw you catch and add to the checklist makes the next run better.
✓
Packaged as a .skill file for installation
Use the skill-creator's package_skill.py or zip the folder yourself. Install in Cowork's Skills panel.
5
Look for the Compound Effect
✓
Identified whether this skill's output feeds another task
A script skill feeds a slides skill. A research skill feeds a proposal skill. Skills that connect become pipelines.

The golden rule

Start with one file. If it gets long, split it. You will feel when it is time. You do not need to get the structure perfect on day one. The skill gets better every time you use it and notice what to fix.

Next step

Ready to go further?

You have the setup. Now learn how to get 10 hours a week back. Claude Cowork Workshop — live, 90 minutes, no jargon. Just hands-on workflows you can use the next morning.

See the workshop →
© 2026 Byte of Brilliance AI. Built by Ekwy Chukwuji.