brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Use before WebSearch to check if you already have the answer, when stuck on an error to find past fixes, or when entering a familiar project to recall past sessions and file changes.
Claude Code
$ npx -y skills add Vvkmnn/claude-historian-mcp --skill claude-historian --agent claude-code
Codex
$ npx skills add Vvkmnn/claude-historian-mcp --skill claude-historian -a codex -y
Cursor
$ npx skills add Vvkmnn/claude-historian-mcp --skill claude-historian -a cursor -y
Gemini CLI
$ npx skills add Vvkmnn/claude-historian-mcp --skill claude-historian -a gemini-cli -y
GitHub Copilot
$ npx skills add Vvkmnn/claude-historian-mcp --skill claude-historian -a github-copilot -y
OpenCode
$ npx skills add Vvkmnn/claude-historian-mcp --skill claude-historian -a opencode -y
Windsurf
$ npx skills add Vvkmnn/claude-historian-mcp --skill claude-historian -a windsurf -y
name: claude-historian description: Use before WebSearch to check if you already have the answer, when stuck on an error to find past fixes, or when entering a familiar project to recall past sessions and file changes.
Search conversation history before starting fresh. You may already have the answer.
**Before WebSearch** → `search(query: "...", scope: "similar")` or `search(query: "...", scope: "conversations")`. Past solutions beat web results.
**Stuck on an error** → `search(query: "<error message>", scope: "errors")`. Finds past fixes with code.
**Entering a familiar project** → `search(scope: "sessions")` for recent work. `search(query: "...", scope: "plans")` for past decisions.
**Working on a familiar file** → `search(scope: "files", filepath: "src/index.ts")`. Shows past changes with context.
| Situation | Tool Call | |-----------|----------| | Error with no obvious cause | `search(query: "<error>", scope: "errors")` | | "Have I done this before?" | `search(query: "...", scope: "similar")` | | Working on familiar file | `search(scope: "files", filepath: "...")` | | Need past design reasoning | `search(query: "...", scope: "plans")` | | What did I do last session? | `search(scope: "sessions")` | | Successful tool workflows | `search(scope: "tools")` | | General search | `search(query: "...", scope: "conversations")` | | Deep-dive into session | `inspect(session_id: "...")` | | Rules, skills, CLAUDE.md | `search(query: "...", scope: "config")` | | Task management history | `search(query: "...", scope: "tasks")` | | Memories across sessions | `search(query: "...", scope: "memories")` |
| Mistake | Fix | |---------|-----| | Going straight to WebSearch | Check historian first — past solutions are more relevant | | Vague queries | Use specific terms: error messages, file paths, tool names | | Using `scope: "all"` for errors | Use `scope: "errors"` — it has dedicated fix extraction | | Long keyword-dump queries | Keep to 3-5 specific terms, not 10+ generic ones |
An Model Context Protocol (MCP) server for searching your Claude Code conversation history. Find past solutions, track file changes, and learn from previous work.
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.