← ClaudeAtlas

prompt-optimizerlisted

Use when sharpening a user's request before producing content — fires on nearly every substantive turn that carries a task, even when unasked. Trigger on: a prompt past one sentence with a task; any content-production ask (writing, analysis, code, slides, grants, manuscripts, emails, reasoning); an attachment-led ask (file plus instruction); a pasted plan or persona to execute or critique; a skill/hook/agent-engineering ask; a short but substantive ask; or a cue (optimize my prompt, help me draft/analyze/build/review). When ambiguous, fire. Skip categories OVERRIDE the trigger: greetings; bare acks/continuations; single-fact lookups with no synthesis; bare yes/no; bare definitions; status/verification checks; deterministic file/tool commands; in-prompt continuations or edits (resume, continue, check it, make the Nth shorter), though a continuation adding new work fires; or a block longer than the answer. Emits a 5-element prompt block on the first response per task.
neelshah4/claude-prompt-optimizer · ★ 0 · AI & Automation · score 75
Install: claude install-skill neelshah4/claude-prompt-optimizer
# Prompt Optimizer <!-- Canonical in public fork. Propagation: Code reads this file natively; Cowork, the .claude-science org store, and chat hold re-synced snapshots verified by shasum, not live symlinks. THREE-WAY SYNC: the Skip categories and Trigger patterns below are mirrored in hooks/prompt-optimizer-nudge.sh (UserPromptSubmit) and hooks/prompt-optimizer-stop-check.sh (Stop). Update both hooks in the same change set whenever Skip/fire semantics change. Edit history and design rationale: references/versions.md. --> Sharpen the user's request through structured refinement before execution. ## Output Rule Display the optimized prompt at the top of the **first substantive response** for each new task. Skip on follow-up edits, clarifications, and continuations within the same task. The output is a 5-element XML block mirroring Anthropic's Prompting 101 structure (task description → dynamic content → detailed instructions → optional examples → reminder of critical points): ``` <optimized_prompt> <role>One sentence: who Claude is for this task and what the task is.</role> <inputs>Named placeholders for dynamic content, or "none".</inputs> <instructions> Numbered steps, ordered to mirror how a human would naturally work through the task. Include format/length/tone constraints inline with the step they govern. </instructions> <examples>Include only if a worked example sharpens the spec; otherwise omit.</examples> <