Spike
Run a disposable experiment to resolve a specific feasibility question. Use for an explicit spike or when inspection cannot resolve an implementation-blocking uncertainty.
Install
npx skills add petekp/claude-code-setup --skill spikegit clone --depth 1 https://github.com/petekp/claude-code-setup.git /tmp/claude-code-setup
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-setup/skills/spike ~/.claude/skills/spikePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Spike State the question, what result would change the decision, and a small experiment budget. Use inspection alone when it can answer the question. A request for a prototype or an estimate does not by itself authorize disposable code or a larger experiment. Keep experiment code separate from the implementation. Use a temporary directory for self-contained checks. If real project imports are needed, use a task-owned, locally ignored scratch directory or an isolated worktree. Preserve unrelated work and the existing scope and approval boundaries. Build only enough to measure the unknown. Do not mock the behavior being measured. Include realistic inputs and failure cases when they could change the answer; skip unrelated production polish. Do not use production credentials or mutate shared data without authorization. Report the observed result, the evidence, its limits, and what it implies for the proposed implementation. A negative result is a valid outcome. Stop when the question is answered or the stated budget is exhausted; do not turn the experiment into an unrequested feature. Record useful findings before removing task-created scratch code. Treat the implementation as separate work; do not silently promote experimental code. If the user asks to retain the prototype or measurement artifact, preserve it and clearly identify its limitations. Never remove someone else's files, branch, or worktree.
Details
- Skill name
spike- Repository
- petekp/claude-code-setup
- Path
skills/spike/SKILL.md- License
- MIT
- Repo updated
- 26 October 2026
FAQ
What does the Spike skill do?
Run a disposable experiment to resolve a specific feasibility question. Use for an explicit spike or when inspection cannot resolve an implementation-blocking uncertainty.
How do I install the Spike skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add petekp/claude-code-setup --skill spike. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Spike popular?
It lives in petekp/claude-code-setup, which has 49 GitHub stars and 10 forks.
Related skills
Catch Up
49petekp/claude-code-setup
Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.
Clean Copy
49petekp/claude-code-setup
Cut interface copy that should not exist. Captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up or tighten copy.
Code Comments
49petekp/claude-code-setup
Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.
Suomen Kieli
31samimiettinen/suomen-kieli
Suomen kielen toimittaja: käytä AINA kun tuotat, käännät, oikoluet, arvioit tai luonnollistat suomenkielistä tekstiä – verkkosivut, dokumentit, markkinointi, asiantuntijaviestintä – tai kun käyttäjä mainitsee oikeinkirjoituksen, kieliopin, pilkutuksen, yhdyssanat tai pyytää oikolukua tai tekstin tarkastusta suomeksi.
Plain
49petekp/claude-code-setup
Restate dense text in plain language. Use when the user asks for a simpler explanation or signals confusion.
Syncable Dependencies
43syncable-dev/syncable-cli
Use when the user asks to audit dependencies, check licenses, list packages, review dependency health, check for copyleft issues, or see prod vs dev dependency split
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.