claude-historian
Automatic history search — checks past sessions before web research, planning, and debugging, siblings deepen coverage
Continuous learning — hooks observe failures and prompt reflection, sibling synergy deepens analysis with history and tool discovery
Claude Code
$ npx -y skills add Vvkmnn/claude-emporium --skill claude-gladiator --agent claude-code
Codex
$ npx skills add Vvkmnn/claude-emporium --skill claude-gladiator -a codex -y
Cursor
$ npx skills add Vvkmnn/claude-emporium --skill claude-gladiator -a cursor -y
Gemini CLI
$ npx skills add Vvkmnn/claude-emporium --skill claude-gladiator -a gemini-cli -y
GitHub Copilot
$ npx skills add Vvkmnn/claude-emporium --skill claude-gladiator -a github-copilot -y
OpenCode
$ npx skills add Vvkmnn/claude-emporium --skill claude-gladiator -a opencode -y
Windsurf
$ npx skills add Vvkmnn/claude-emporium --skill claude-gladiator -a windsurf -y
name: claude-gladiator description: Continuous learning — hooks observe failures and prompt reflection, sibling synergy deepens analysis with history and tool discovery triggers: [PostToolUse, Stop]
Continuous learning. Observes tool failures and prompts reflection at session end to evolve rules, hooks, and skills.
| Hook | When | Action | |------|------|--------| | **PostToolUse(Bash\|Edit\|Write)** | After tool failure | Observes the error pattern (silent on success) | | **Stop** | Session ending | Prompts reflection if unprocessed observations exist |
| Command | Description | |---------|-------------| | `/review-gladiator [topic]` | Batch learn from accumulated observations and session history |
Tool failures trigger observation automatically:
gladiator_observe(
summary: "<what failed and how it was fixed>",
context: {error, tool, before, after},
tags: ["error", "<tool_name>"]
)1. `gladiator_reflect()` — cluster observations into recommendations 2. For each recommendation: read the existing artifact (if overlap detected) 3. Propose UPDATE to existing artifact, not a new duplicate 4. Present to user with reasoning 5. Apply changes one at a time after approval
1. If **historian** active: enrich reflection with broader context
2. `gladiator_reflect()` — cluster observations 3. If **oracle** active: for each recommendation involving new artifacts
4. Present enriched recommendations: pattern + history + available tools 5. Apply changes one at a time after approval
1. If **historian** active: `list_recent_sessions()` to get session refs 2. `gladiator_observe(source: "conversation", session_ref: <ref>)` for relevant sessions 3. `gladiator_reflect()` to cluster all observations 4. If **oracle** active: search for existing solutions before creating new 5. Present recommendations to user
| Sibling | Value | How | |---------|-------|-----| | **Historian** | Past solutions enrich reflection | `get_error_solutions()`, `search_conversations()`, `find_tool_patterns()` | | **Oracle** | Existing tools found before creating new | Search oracle for best-in-class solutions during reflection | | **Praetorian** | n/a | Gladiator has its own persistence | | **Vigil** | n/a | Different concerns (files vs patterns) |
| 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 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
Prompt rhetoric coach — deterministic scoring and restructuring using Anthropic best practices
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.