Craft Skill

A skill should be called for the right task, steer the agent to genuine completion, and make every token earn its place.

Establish the job

Read the request, conversation, existing skill, repository conventions, and target platform's authoritative skill specification.

Define the useful behavior with realistic examples: what should call the skill, what should not, what the agent should do differently, and what observable evidence means it finished. Ask only about user-owned choices that materially change those answers. When revising a skill, preserve its name and inspect observed failures before editing.

Call

• Follow the platform's metadata and invocation contract. Test triggering only when automatic invocation exists.
• Make the description identify the skill and its distinct trigger branches without leaking enough procedure to skip the body. One trigger per real branch; synonyms are not branches.
• Keep what every branch needs in SKILL.md. Put branch-specific knowledge behind a direct pointer that states when to load it.

Call is complete when every intended branch and close non-trigger has one clear owner, and the metadata passes the platform's validator when one exists.

Steer