The skill card and the three-skill split (free sample)

Here is a job I have done three times [paste notes]. Draft a SKILL.md from this card.
Then tell me whether it should be split into a reference lock, a plan and a build and critique skill, and why.

Fill May not yourself.

# The skill card and the three-skill split (free sample)

A free sample from Agent Skills Workshop by PaperChaseWebb. Works with Hermes Agent, Claude Code, Codex, Grok Bot or any harness that reads SKILL.md skills.

Skills written once now load in many harnesses. That makes a sloppy skill expensive: it runs everywhere. These two pieces fix most of the early mistakes.

## The skill card

Fill this before you write a single step.

```
---
name: [verb + object, for example "draft weekly client report"]
description: [one line: WHEN to use this, written for the harness deciding whether to load it]
---
# Purpose
[One sentence on the outcome.]

# Inputs
- [What the skill needs before it starts. If missing, stop and ask.]

# Steps
1. [Short, checkable step.]

# Done means
- [The check that proves it finished.]

# May not
- [Actions this skill never takes.]

# Action class
[read / draft / change / outward]
```

The description line does more work than any step. Write it as "Use when..." with the words you actually type.

## The three-skill split for long jobs

| Skill | Job | Why separate |
|---|---|---|
| Reference lock | Freeze the few examples, specs or rules the work must match | Every later step compares to the same few things |
| Plan with timings | Ordered steps with a time or size budget each | Long jobs fail on order and scope |
| Build and critique | Build one piece, then a separate check compares it to the references, with a round limit | A builder reviewing its own work agrees with itself |