skill-publishinglisted

# skill-publishing How to write a good agent skill and publish it so others (and your other machines) can install it with `npx skills`. ## What a skill is Reusable, **on-demand context** for an AI coding agent. One skill = one folder with a `SKILL.md`: ```markdown --- name: my-skill # kebab-case, matches the folder description: <one line> # the TRIGGER — see below; most important field metadata: author: you version: "1.0.0" # semver; bump on meaningful change --- # Title <the body the agent loads only when this skill fires> ``` **Context economy:** only the `description` of every installed skill stays in the agent's context. The body loads **only when the description matches** the task. That's the whole design — so the description does the heavy lifting. ## The `description` is the trigger (get this right) Write it as **concrete triggers**: what it does, then "Use when …" listing symptoms, situations, and phrases a user might actually say. - Good: `…Use when an iPhone page shows black bars, content is cut off at the bar edge, a cropped shadow, or the page jumps after the keyboard closes.` - Bad: `Helps with iOS Safari styling.` If the agent won't *match* it to the right moment, the skill is dead weight. ## The body - Write for the **agent**, not end users: actionable facts, steps, rules. - **Scannable**: headings, short sections, tables, code blocks. - **Progressive disclosure**: keep `SKILL.md` focused; put heavy reference docs or sc