// Continuous learning — INVOKE after sessions with many errors or corrections to record patterns and improve rules, hooks, and skills
| name | claude-gladiator |
| description | Continuous learning — INVOKE after sessions with many errors or corrections to record patterns and improve rules, hooks, and skills |
| triggers | ["PostToolUseFailure","Stop"] |
Continuous learning. Observes tool failures and prompts reflection to evolve rules, hooks, and skills.
| Hook | When | Action |
|---|---|---|
| PostToolUseFailure(Bash/Edit) | After tool failure | Nudges you to call gladiator_observe() — you must call it, not automatic |
| Stop | Session ending | Prompts gladiator_reflect() if >= 10 unprocessed observations |
| Command | Description |
|---|---|
/review-gladiator [topic] | Batch learn from accumulated observations and session history |
After a tool failure, the hook nudges you. YOU must call gladiator_observe() — it is NOT automatic. After fixing an error, record what worked:
gladiator_observe(
summary: "<what failed and how it was fixed>",
context: {error, tool, before, after},
tags: ["error", "<tool_name>"]
)
gladiator_reflect() — cluster observations into recommendationsgladiator_reflect() to cluster all observations| Situation | Call |
|---|---|
| Tool failure (auto) | gladiator_observe(summary, context={error, tool, before, after}, tags=["error", tool]) |
| User correction | gladiator_observe(summary, context={before, after}, tags=["correction"]) |
| Convention found | gladiator_observe(summary, tags=["convention", "domain"]) |
| Decision made | gladiator_observe(summary, tags=["architecture", "decision"]) |
claude mcp add gladiator -- npx claude-gladiator-mcp
Automatic tool discovery across 19 sources — INVOKE before planning, before adding dependencies, or when looking for tools to discover relevant skills, plugins, and MCP servers
Use after writing or editing a plan file, after exiting plan mode, or when asked "why did you choose this?" — surfaces decisions, risks, and blind spots before implementation.
Session history search — INVOKE before planning, before web research, after errors, or when looking for past conversation content. Use INSTEAD of manually grepping .jsonl session files.
Cross-session memory - save insights after research, restore context at session start. Reduces re-exploration and prevents token waste.
File checkpoint and recovery — auto-quicksaves before destructive commands, INVOKE before implementing a plan or starting risky multi-file changes. Also use when user asks to undo changes or compare current state to a prior checkpoint.
Prompt rhetoric coach — deterministic scoring and restructuring using Anthropic best practices