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