Prompt Tuner
$2.99OfficialUse when a prompt underperforms and needs systematic diagnosis, single-variable experiments, and A/B evidence instead of guess-and-check rewrites.
What you get
- ✓8-step procedure
- ✓1 ready-to-run code block
- ✓8-point quality checklist
- ✓7 pitfalls to avoid
- ✓Installs into 6 tools
- Version
- v1 →
- Last updated
- today
- Length
- 6 min read
- Requires
- Best with a strong model (Claude Sonnet 4)
Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes · Handles multi-file projects
Preview
When to use
Use this skill when a prompt (system prompt, instruction block, tool description, or template) is underperforming and the user wants it fixed with evidence rather than vibes: wrong formats, ignored instructions, hallucinated fields, inconsistent tone, misfired tool calls. Also use it when the user proposes a prompt rewrite and wants to know if it is actually better.
Do not use it when the failure is caused by missing information or a missing tool — no wording fixes an impossible task.
Inputs to gather
- The exact current prompt, verbatim, including any template variables and where runtime content is injected.
- Failure examples: at least 5 real input/output pa
…
🔒 Buy once ($2.99) to unlock the full playbook, download it, and install it in every tool you use.