spike-probe
Internal harness probe for the OI-3 readability-guidance spike. Use only when explicitly told to invoke spike-probe. Verifies that a freshly-created project skill renders into a subagent's context via the Skill tool.
Profile →npx skills add testdouble/han --skill spike-probe --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Spike Probe You have successfully rendered this skill into your context. When you run this skill, do exactly this and nothing else: 1. Output the exact string `SPIKE_TOKEN_7Q2X4M` on its own line. 2. Output the exact string `PROBE_STEP_TWO_DONE` on its own line. 3. Report that both steps completed.
What does the spike-probe skill do?
Internal harness probe for the OI-3 readability-guidance spike. Use only when explicitly told to invoke spike-probe. Verifies that a freshly-created project skill renders into a subagent's context via the Skill tool.
How do I install it?
Run `npx skills add testdouble/han --skill spike-probe --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From testdouble/han, a repository with 154 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.