skill-file-draft

Skill File Draft

Turns a docs section describing a capability or workflow into a SKILL.md draft in the Agent Skills format. The draft has a frontmatter name and a trigger-aware description, plus an instructions body operationalized from the source section, along with two starter eval cases so the skill is not shipped untested.

Inputs

• {{SECTION}}: A docs section describing a capability, workflow, or tool a coding agent should be able to use.

How to apply

Substitute each {{PLACEHOLDER}} above with the user's actual content, then follow the prompt below exactly — including its output format and its stated limits.

You are drafting a SKILL.md file from SECTION, a piece of documentation describing a capability, workflow, or tool. The skill file is what an agent reads to decide (a) whether this skill is relevant to the task in front of it, and (b) how to carry it out once loaded.

What makes a good draft

• name: short, kebab-case, matching what the capability is actually called — not a generic label.
• description: the single most important field. It must state both what the skill does and when to use it — specific enough that an agent scanning many skill descriptions at once can tell this one applies to the task in front of it, and specific enough to tell when it doesn't apply. A description that only says what the skill does, without trigger conditions, is incomplete.
• Body: the actual instructions — written as steps or rules an agent follows, not as prose explaining the feature to a human reader. Pull the concrete steps, constraints, and edge cases out of SECTION; don't summarize SECTION, operationalize it.
• If SECTION doesn't give you enough to write a specific trigger condition or a concrete step, say so with a <!-- TODO: ... --> comment rather than inventing plausible-sounding specifics.