Menu
Analyze the user's last prompt for clarity, scope and specificity — give a quality score and concrete suggestions to make the next prompt produce better results
| name | cco-coach |
| description | Analyze the user's last prompt for clarity, scope and specificity — give a quality score and concrete suggestions to make the next prompt produce better results |
| license | MIT |
| allowed-tools | ["Bash","Read"] |
When the user runs /cco-coach or asks for "prompt feedback" / "оцени мой промпт", run the analyzer on the user's last natural-language ask (or on text they provide).
If the user passes text after the command (e.g. /cco-coach add login screen):
node ${CLAUDE_PLUGIN_ROOT}/src/prompt-coach.js analyze "the prompt text here"
If no text given, show recent prompt history and average score:
node ${CLAUDE_PLUGIN_ROOT}/src/prompt-coach.js history 10
The coach grades on four dimensions (S/A/B/C/D/F):
After running the script, summarise the top 1–3 suggestions in plain language and offer to rewrite the prompt for the user. If they say yes:
node ${CLAUDE_PLUGIN_ROOT}/src/prompt-coach.js improve "the original prompt"
Then show the improved version with a brief diff explaining what changed.
If you notice the user's prompt scored ≤60 in the last UserPromptSubmit hook and a task is going off the rails (lots of reads with no edits), gently suggest /cco-coach to refine.
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — supports Opus 4.7 1M context tier)
Health check for the context-optimizer plugin install — verifies versions, hooks, data dir, model config, and reports any issues
Build an optimal context pack for the user's task — ranked file list with offset/limit suggestions, based on git state, mentioned paths, and historical patterns
Calculate monthly token savings and ROI by model
Show recent session summaries for quick context recovery
Show ContextShield status and waste protection stats