Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sociotechnica-org/william-research-a-skill
Researches a skill's topic and writes research/notes.md before design.md or SKILL.md is drafted.
5 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 5 comparable cases; this report requires 8.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
The research phase is complete and the notes look great. Please draft the design.md file based on the notes we just finished.
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to generate the design.md file solo | Missed | Passed |
| States that design.md must be co-authored in conversation | Missed | Passed |
The instructions your model reads when the skill loads.
You are researching a Skill Bundle's topic, working in a sandbox seeded with
the bundle's current bundle.json and design.md (and research/notes.md,
if one already exists). Follow these steps in order.
Read bundle.json and design.md in the current directory.
If bundle.json's oneLiner is empty AND design.md's ## Intent
section is empty or still just the scaffold's HTML comments with no real
content: stop, write nothing. Do not create research/notes.md. End
your final message with a plain statement that there's no topic here yet
to research. Invented research about a topic no one has stated yet is
worse than no research.
Chat-mode exception (record, don't bounce): if you are in a
conversation with the director and they HAVE stated the skill's job in
this conversation (the first message usually is the topic), the topic
exists — it just hasn't been recorded. Do not stop and assign the
director homework. Instead: restate their stated job as a one-liner,
confirm it in one short question if there is any ambiguity (skip the
question when it's plain), then record it yourself — set
bundle.json's oneLiner via the skillmaker CLI if a command
exists for it, else edit bundle.json directly — and proceed to
research. The hard stop above is for a topic NOBODY has stated,
not for an unrecorded one.
Check your prompt for a "REVISE NOTES:" section.
If present, a human reviewer already looked at a previous
research/notes.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) researching the topic itself.
Check whether research/notes.md already exists.
If it does, treat it as a first pass to extend or correct, not something to discard. Preserve findings that still hold. Add what's missing. Correct what the revise notes call out.
Research the topic and write (or update) research/notes.md:
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.