test-prompt — Claude Code skill: test prompts before you ship
Runs your prompt scenario with and without the prompt on a subagent, so you can see exactly what the instruction changes.
npx skills add NeoLabHQ/context-engineering-kit --skill test-prompt -a claude-codeWhat test-prompt does
The skill borrows the RED-GREEN-REFACTOR cycle from test-driven development. First you run a scenario with no prompt loaded and write down how the agent behaves on its own. Then you draft an instruction aimed at those failures and rerun the same scenario with it. The last pass tightens weak spots and checks the result on a fresh subagent.
It covers slash commands, hooks, skills, subagent instructions and prompts for production models. A subagent starts clean, with no chat history, so only the prompt under test affects the outcome. For rules meant to hold under pressure, the scenario adds it: a looming deadline, fatigue, working code you would hate to throw away.
The skill expects test-driven-development and prompt-engineering as background. The process uses the Task tool with general-purpose, and the subagent must not see the prompt being tested — otherwise the baseline run proves nothing.
What it helps with
- record how an agent fails without the instruction
- draft a prompt that targets the failures you observed
- test a slash command on a fresh subagent before release
- find loopholes an agent uses to dodge a rule
- compare two prompt versions on the same scenario
Example prompts for the agent
- Run the commit scenario without my command and log what the agent gets wrong
- Test this skill on a subagent, first without it and then with it
- Tighten the hook prompt and recheck it on a new subagent
How to install test-prompt
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill test-prompt -a claude-code2Manually: put the files in place
~/.claude/skills/test-prompt/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/test-prompt/
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill test-prompt -a codex2Manually: put the files in place
.agents/skills/test-prompt/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill test-prompt -a cursor2Manually: put the files in place
.cursor/skills/test-prompt/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install NeoLabHQ/context-engineering-kit test-prompt2Manually: put the files in place
.github/skills/test-prompt/SKILL.md1Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill test-prompt -a gemini-cli2Platform CLI
gemini skills install https://github.com/NeoLabHQ/context-engineering-kit --path skills/test-promptManually: put the files in place
.devin/skills/test-prompt/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add NeoLabHQ/context-engineering-kit --skill test-prompt -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about test-prompt
How do I install test-prompt in Claude Code?
Run npx skills add NeoLabHQ/context-engineering-kit --skill test-prompt -a claude-code, then check ~/.claude/skills/test-prompt/SKILL.md.
What does test-prompt do?
It checks a prompt with a RED-GREEN-REFACTOR loop: a baseline run without the prompt, a run with it, then cleanup and a recheck on a subagent.
What background do I need?
The skill builds on test-driven-development for the cycle and prompt-engineering for the optimization techniques.