Skill Authoring Agent Skill

Skill authoring

A skill is judged twice: on whether it loads at the right moment, and on whether it helps once

loaded. Most fail the first test.

The description does the triggering

It is the only part read when deciding whether to load. Write it for that job:

• Lead with what the skill does, in one clause.
• Then when to reach for it — the situations, in the words someone would actually use, including

the oblique ones ("why isn't this converting" as well as "CRO audit").

• Name the edge cases that should still trigger it, and where useful, what should *not*.

Vague descriptions produce two failures at once: the skill misses cases it should catch, and fires

on cases it cannot help.

The body does the work

Write for someone competent who has not thought about this problem today. That means:

• Method over exhortation. "Be thorough" is noise. An ordered procedure is instruction.
• State the failure behind each rule. A rule with no failure attached gets optimized away by the

next reader.

• Be specific enough to be wrong. Guidance too hedged to contradict is too vague to follow.
• Put long material in references/ and say when to read it. The body should fit in working

memory.

Overlap is the silent killer

Two skills whose descriptions both match a request means neither reliably wins. Before adding one,

check what already covers the ground. Prefer extending an existing skill, or consolidating the

family into one skill with references, over adding a near-neighbor.

Mechanics

• name must be lowercase-hyphenated and equal the directory name, or the skill will not load.
• One skill, one directory, SKILL.md at its root; supporting material in references/ and

scripts/.

Verify before shipping

Write three requests that should trigger it and two that should not, and check the description

actually discriminates. If a near-miss request would pull it in, tighten the description.