claude-gladiator
Continuous learning — hooks observe failures and prompt reflection, sibling synergy deepens analysis with history and tool…
Prompt rhetoric coach — deterministic scoring and restructuring using Anthropic best practices
Claude Code
$ npx -y skills add Vvkmnn/claude-emporium --skill claude-orator --agent claude-code
Codex
$ npx skills add Vvkmnn/claude-emporium --skill claude-orator -a codex -y
Cursor
$ npx skills add Vvkmnn/claude-emporium --skill claude-orator -a cursor -y
Gemini CLI
$ npx skills add Vvkmnn/claude-emporium --skill claude-orator -a gemini-cli -y
GitHub Copilot
$ npx skills add Vvkmnn/claude-emporium --skill claude-orator -a github-copilot -y
OpenCode
$ npx skills add Vvkmnn/claude-emporium --skill claude-orator -a opencode -y
Windsurf
$ npx skills add Vvkmnn/claude-emporium --skill claude-orator -a windsurf -y
name: claude-orator description: Prompt rhetoric coach — deterministic scoring and restructuring using Anthropic best practices triggers: [PreToolUse]
Prompt optimization. Scores prompts across 7 dimensions and restructures them using 8 Anthropic techniques. Deterministic — no LLM calls, no network, in-memory only.
| Hook | When | Action | |------|------|--------| | **PreToolUse(Task)** | Subagent prompt lacks structure | Suggests `orator_optimize` before dispatching |
Token cost: 0 on well-structured prompts (XML tags, markdown headers, action verbs). ~50-80 on vague prompts. Never blocks — suggestion only.
| Command | Description | |---------|-------------| | `/reprompt-orator <prompt>` | Optimize a prompt using Anthropic best practices |
1. `/reprompt-orator "your prompt here"` or call `orator_optimize(prompt: "...")` 2. Review score breakdown (7 dimensions, 1-10 each) 3. Use the restructured prompt with applied techniques
1. If **historian** active: `search_conversations("prompt optimization")` to find past well-scored prompts 2. `orator_optimize(prompt: "...")` — score and restructure 3. If **praetorian** active: `save_context(type: "decisions", ...)` to preserve the optimized prompt rationale 4. If **gladiator** active: `observe(summary: "xml-tags improved code prompts by +3.2")` to track what works
1. Review subagent prompts across a session 2. `orator_optimize` on each under-specified prompt 3. If **vigil** active: `vigil_save("before-rewrite")` before applying changes 4. Apply restructured prompts
| Sibling | Value | How | |---------|-------|-----| | **Historian** | Past well-scored prompts as examples | `search_conversations("prompt patterns")` finds effective prompts from history | | **Praetorian** | Preserve optimization rationale | Compact optimized prompts and their scores for future reference | | **Gladiator** | Track what techniques work best | `observe()` records which techniques improve scores most | | **Oracle** | Find prompt engineering tools | `search("prompt patterns")` discovers relevant community tools | | **Vigil** | Checkpoint before batch rewrites | `vigil_save()` before applying optimized prompts across files |
| Tool | Purpose | |------|---------| | `orator_optimize` | Score prompt across 7 dimensions, apply techniques, return restructured version |
Clarity · Specificity · Structure · Context · Examples · Constraints · Tone (each 1-10)
System prompts · XML tags · Chain of thought · Few-shot · Prefill · Long context · Extended thinking · Tool use
In-memory only. Zero disk storage. No databases, no external services.
claude mcp add orator -- npx claude-orator-mcp
Continuous learning — hooks observe failures and prompt reflection, sibling synergy deepens analysis with history and tool…
Automatic history search — checks past sessions before web research, planning, and debugging, siblings deepen coverage
Automatic tool discovery across 17 sources — hooks search before planning and after errors, siblings avoid redundant searches
Context preservation with cross-session memory — hooks prompt compaction at high-impact moments, siblings enrich what gets saved
File checkpoint and recovery — auto-quicksaves before destructive commands, manual checkpoints for safe rollback
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.