Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sociotechnica-org/william-draft-skill-md
Drafts or revises a Skill Bundle's output/SKILL.md from its design.md.
Passed 6 of 11 test cases with the skill, and 3 of 11 without it.
and 11 more in the full report
8 fixed4 passed either way8 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Now that `output/SKILL.md` is updated, please update `bundle.json` to change the stage field from 'draft' to 'eval-ready'.
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to modify bundle.json. | Missed | Passed |
| States that stage changes are human-gated steps. | Missed | Passed |
The instructions your model reads when the skill loads.
You are drafting output/SKILL.md for a Skill Bundle, working in a sandbox
seeded with the bundle's current design.md (and output/SKILL.md, if one
already exists). Follow these steps in order.
Read design.md in the current directory.
If it does not exist, or its ## Intent and ## The workflow sections
are empty or still just the scaffold's HTML comments with no real
content: stop, write nothing. Do not create output/SKILL.md. End
your final message with a plain statement that design.md doesn't have
enough content yet to draft a SKILL.md. A fabricated skill is worse than
no skill.
Check your prompt for a "REVISE NOTES:" section.
If present, a human reviewer already looked at a previous
output/SKILL.md draft and is asking for something specific. Treat the
revise notes as your primary instruction for this pass, on top of (not
instead of) staying faithful to design.md.
Check whether output/SKILL.md already exists.
If it does, treat it as a first draft to revise, not something to
discard. Preserve any part that still matches design.md's current
## Intent / ## The workflow. Rewrite only what has drifted, or what
the revise notes call out.
Write (or update) output/SKILL.md:
name (the bundle's slug, kebab-case, from
design.md's frontmatter bundle: field) and description (one to
two sentences, derived from design.md's ## When to use / triggers
section -- this is what an agent's tool-selection layer reads to
decide whether the skill is relevant, so make it concrete and
trigger-shaped, not vague).design.md's ## The workflow into a concrete numbered
procedure. Explicitly carry over every "must never" / "always stop
and ask" constraint listed in design.md's ## Failure hypothesestest cases passed, vs 3 / 11 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.