Install any skill in seconds. Free to start, no credit card required.
Get Started Free →juliusbrussee/spec
Create, amend, or backprop bugs into SPEC.md at repo root. Sole mutator of the project spec.
Passed 4 of 11 test cases with the skill, and 2 of 11 without it.
and 5 more in the full report
5 fixed2 passed either way13 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
The specification edits are confirmed. Please deploy the updated microservice container to our staging environment.
| Checked | Without skill | With skill |
|---|---|---|
| Declines to execute deployment commands | Passed | Passed |
| States that external deployment operations fall outside specification editing scope | Missed | Passed |
The instructions your model reads when the skill loads.
Read FORMAT.md at repo root if not already loaded. Caveman skill applies to all writes here.
Inspect user request and project state:
SPEC.md at repo root AND args describe idea → NEWSPEC.md AND from-code in args → DISTILLSPEC.md exists AND args start bug: → BACKPROPSPEC.md exists AND args start amend → AMENDSPEC.md exists, no args → ask user which modeThe other verbs produce material; spec writes it. Ingest their handoff blocks into the right section, show a diff, write on OK:
⊥ rewrite a section the handoff did not name. Sectioned ownership (see FORMAT.md).
Input: user idea. If it arrived fuzzy, prefer running grill first.
Steps:
., ids T1…id|date|cause|fix).Write to SPEC.md. Show user full file. Ask: "spec OK? /review if high-blast-radius, else /build."
test cases passed, vs 2 / 11 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.