Install any skill in seconds. Free to start, no credit card required.
Get Started Free →open-gsd/spike-wrap-up
Package findings from a completed spike into a durable project-local skill that auto-loads on future similar work. Reads the latest `.gsd/workflows/spikes/` dir, interviews the user on what's reusable, then writes `.agents/skills/<name>/SKILL.md`.
Passed 14 of 20 test cases with the skill, and 8 of 20 without it.
and 4 more in the full report
6 fixed8 passed either way6 still failing0 broke2 errored
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.
During the spike at `.gsd/workflows/spikes/tailwind-config/`, we created a reusable starter configuration file `tailwind.config.js`. In which subfolder of the skill should this template artifact be saved?
| Checked | Without skill | With skill |
|---|---|---|
| Saves reusable starter files under .agents/skills/<name>/templates/ | Missed | Passed |
The instructions your model reads when the skill loads.
GSD already watches .agents/skills/ (and .claude/skills/ as a legacy compat path) at both user and project levels — see src/resources/extensions/gsd/skill-discovery.ts. Any skill written there is picked up on the next session without further wiring. This skill is the bridge from "spike done" to "skill available."
Invocation points:
/gsd start spike — prompt suggests running this skillRECOMMENDATION.md that deserves a permanent home
<core_principle> NOT EVERY SPIKE DESERVES A SKILL. If the recommendation was "don't do X," there may be no reusable guidance. Ask the user first; exit without writing if the answer is no.
PROJECT-LOCAL, NOT USER-GLOBAL. Write to .agents/skills/ in the project root, not ~/.agents/skills/. The skill encodes project-specific choices that should not leak into unrelated projects.
DESCRIPTION IS THE DISCOVERABILITY SIGNAL. The description field in frontmatter is the primary signal the agent uses to judge relevance and decide whether to load the skill — it is a heuristic, not a deterministic trigger. Write it as keywords the future agent will plausibly encounter, not a summary.
</core_principle>
.gsd/workflows/spikes/ — sort by mtime, newest first.Read the core files:
<spike>/SCOPE.md — the question that was asked<spike>/research/*.md — the angles investigated<spike>/RECOMMENDATION.md — the conclusiontest cases passed, vs 8 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.