prompter

Evaluates and rewrites user prompts for clarity and actionability before Claude Code executes them.

32|4|Updated May 6, 2026
One-click install
npx skills add https://github.com/Terryc21/prompter --skill prompter-terryc21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prompter
Source: https://github.com/Terryc21/prompter
Command: npx skills add https://github.com/Terryc21/prompter --skill prompter-terryc21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Short, grammatically fine prompts are often under-specified along the dimensions that matter, so Claude Code runs in a direction you didn't choose and the next turn is spent reorienting. This Skill intercepts prompts before execution, evaluates whether a rewrite would meaningfully improve them, and shows the rewrite for approval first. ## Core Features & Use Cases - Evaluate-first rewriting: Only rewrites when there is a real improvement — typos, ambiguous references like "that file", vague intent, or missing guardrails — and emits a skip notice otherwise. - Approval-gated rewrites: Displays the rewritten prompt with a "Rewritten prompt:" prefix and waits for your approval before acting. - Flexible activation modes: Try it once, apply for the whole session, or persist the behavior by adding a Prompt Rewriting rule to your project's CLAUDE.md (with safe detection, diffing, and removal of existing sections). - Use Case: You type "the tests are flaky, fix them" and the Skill rewrites it into a structured diagnosis task — categorize each flake by type, produce a ranked table, and don't apply fixes yet — before any code is touched. ## Quick Start Ask Claude to run the prompter skill, choose "Try it once", then submit a short prompt like "the tests are flaky, fix them" to see the proposed rewrite.

Frequently Asked Questions about prompter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rewrite prompts automatically in Claude Code?▼

Install the prompter skill into ~/.claude/skills/ and run /skill prompter in a session. It evaluates each prompt, shows a rewrite when warranted, and waits for your approval before Claude acts on it.

How do I make prompt rewriting persist across Claude Code sessions?▼

Choose the "Add to CLAUDE.md" mode when invoking the skill. It inserts a Prompt Rewriting section into your project's CLAUDE.md that points back to the skill file, so the behavior applies in all future sessions for that project.

Does the prompt rewriter change every prompt I type?▼

No. It only rewrites when there is a real improvement, such as typos, ambiguous references, or vague intent. Permission responses, option selections, follow-up answers, and already-clear prompts are skipped with a one-line notice.

Can I remove the Prompt Rewriting rule from CLAUDE.md?▼

Yes. Run the skill and choose "Remove from CLAUDE.md". It locates the section by its heading, removes clean template blocks directly, and asks for confirmation if the block was modified.

What are the limitations of automatic prompt rewriting?▼

The skill is stateless and does not learn your style across sessions, and it intentionally does not generate code or make architectural decisions. It only rewrites the next prompt for clarity and waits for approval.