Skip to main content
skill CX Codex

claude-historian — Claude Code skill: session history search

claude-historian — a skill that automatically searches past sessions before triggering web research, planning, or debugging. Reuse past solutions across projects and avoid redundant work.

MIT ★ 78 updated 2026-03-05

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add Vvkmnn/claude-emporium
/plugin install claude-historian@claude-emporium
Open on GitHub

What claude-historian does

claude-historian intercepts tools—web search, planning, agent tasks, error handling—and checks your session history first. Looking for data you found before? It checks. Fixing an error you've already solved? It finds the old fix.

The skill has six functions: full-text search across all sessions, related past queries, error solutions, file context tracking, workflow discovery, and recent session browsing. Four hooks catch the moment before web research, planning, task execution, and post-error feedback. It requires the MCP server claude-historian-mcp.

Works better with sibling skills. Praetorian compacts history into dense context after searches. Oracle finds tools for error classes when patterns emerge. Gladiator enriches observations with historical patterns. Vigil preserves file state alongside session memory.

What it helps with

  • recall how you fixed an error instead of debugging from scratch
  • remember which API you integrated three projects ago
  • avoid re-searching for answers you already found
  • connect similar solutions across different codebases
  • bridge past context with current debugging

Example prompts for the agent

  • Search how I parsed CSV before
  • /search-historian why did nginx crash with memory leak
  • Show me past solutions for this error pattern

How to install claude-historian

1Plugin marketplace

/plugin marketplace add Vvkmnn/claude-emporium
/plugin install claude-historian@claude-emporium

This installs the whole claude-historian plugin with all its skills

2Skills CLI (Vercel)

npx skills add Vvkmnn/claude-emporium --skill claude-historian -a claude-code

3Manually: put the files in place

~/.claude/skills/claude-historian/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/claude-historian/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about claude-historian

How do I install claude-historian in Claude Code?

Run three commands in order: /plugin marketplace add Vvkmnn/claude-emporium, then /plugin install claude-historian@claude-emporium, then npx skills add Vvkmnn/claude-emporium --skill claude-historian -a claude-code. Config saves to ~/.claude/skills/claude-historian/SKILL.md.

What does claude-historian do?

It checks past sessions before you start web research, planning, or debugging. If a similar task was solved before, it shows the old solution. If an error recurs, it finds how you fixed it previously.

Does claude-historian work with other skills?

Yes. It pairs best with Praetorian (compacts history into context), Oracle (finds tools for error classes), and Gladiator (enriches patterns with history). Each amplifies coverage.

Source text

SKILL.md · MIT
---
name: claude-historian
description: Automatic history search — checks past sessions before web research, planning, and debugging, siblings deepen coverage
triggers: [PreToolUse, PostToolUse]
---

# Historian Plugin

Session memory. Checks past sessions before redundant research, planning, or debugging.

## Hooks

| Hook | When | Action |
|------|------|--------|
| **PreToolUse(WebSearch/WebFetch)** | Before web research | Checks `find_similar_queries()` first |
| **PreToolUse(EnterPlanMode)** | Before planning | Searches `search_plans()` for past approaches |
| **PreToolUse(Task)** | Before agents | Checks `find_tool_patterns()` for workflows |
| **PostToolUse(Bash)** | After errors | Suggests `get_error_solutions()` |

## Commands

| Command | Description |
|---------|-------------|
| `/search-historian <query>` | Search past sessions for solutions, decisions, context |

## Workflows

### Search (standalone)

1. `search_conversations("query")` — full-text across all sessions
2. If error-related: `get_error_solutions("error pattern")`
3. If file-related: `find_file_context("filename")`
4. Summarize relevant findings

### Search (with siblings)

1. `search_conversations("query")` — historian's own search
2. If **praetorian** active: `praetorian_restore("query")` for compacted context (denser than raw history)
3. If **oracle** active: `search("query")` when error patterns suggest a missing tool
4. Combine: historian provides breadth (all sessions), praetorian provides depth (curated insights)

### Error Resolution (standalone)

1. `get_error_solutions("error pattern")` — how was this fixed before?
2. If found: apply the previous solution
3. If not: proceed with normal debugging

### Error Resolution (with siblings)

1. `get_error_solutions("error pattern")` — historian checks past fixes
2. If **oracle** active: `search("error tool")` for tools that address this error class
3. If **gladiator** active: check if this error was already observed as a pattern
4. Present combined findings: past fix + available tools + pattern context

## Sibling Synergy

| Sibling | Value | How |
|---------|-------|-----|
| **Praetorian** | Research will be compacted after | Praetorian prompts saving after web searches historian triggers |
| **Oracle** | Tools found for error patterns | Oracle searches for tools when historian finds recurring errors |
| **Gladiator** | Observations correlate with history | Past solutions enrich gladiator reflection |
| **Vigil** | Checkpoints complement history | File state preserved alongside session history |

## MCP Tools Reference

| Tool | Purpose |
|------|---------|
| `search_conversations` | General history search |
| `find_similar_queries` | Find related past questions |
| `get_error_solutions` | Find how errors were fixed |
| `find_file_context` | Track file changes |
| `find_tool_patterns` | Discover successful workflows |
| `list_recent_sessions` | Browse recent work |
| `search_plans` | Find past implementation plans |

## Requires

```
claude mcp add historian -- npx claude-historian-mcp
```

© vvkmnn · MIT · Vvkmnn/claude-emporium

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set20

The whole set →
claude-oracle claude-oracle searches 17 sources for relevant skills, plugins, and MCP servers. It runs before planning and after Bash errors. CX Codex +1 ★ 78repo stars claude-praetorian claude-praetorian — a skill that snapshots your context before it gets compacted and brings it back later: before planning, after web research, when a subagent finishes. CX Codex +1 ★ 78repo stars claude-vigil claude-vigil saves file checkpoints and automatically quicksaves code before risky bash operations like rm or git reset. Roll back edits whenever an agent command goes wrong. CX Codex +1 ★ 78repo stars claude-orator claude-orator scores prompts across seven dimensions and returns a reworked version. Use it to shape subagent requests or review prompts across a session. CX Codex +1 ★ 78repo stars claude-gladiator claude-gladiator tracks tool failures, collects observations, and prompts reflection to update rules and skills at session end. It helps the agent learn from its own mistakes. CX Codex +1 ★ 78repo stars claude-orator claude-orator is a Claude Code plugin that scores and restructures prompts before they go to subagents. Its hook suggests a rewrite for underspecified Task prompts. ★ 78repo stars claude-vigil claude-vigil creates file snapshots before destructive operations, shows what changed, and restores safely. Protection against accidental deletion or overwriting. ★ 78repo stars claude-gladiator claude-gladiator is a Claude Code plugin that catches tool failures and prompts reflection before sessions close. ★ 78repo stars

Project sponsors

Companies that keep this analytics open