session-historian
Look up prior Claude Code sessions when context is lost or forgotten. Use when asked "what did we do before?", "what happened in the last session?", "I forgot what we were working on", "find what I told you about X", or any request to recall past conversation history, prior decisions, experiments, or outcomes. Searches raw JSONL transcripts from ~/.claude/projects/ via DuckDB index. Returns verbatim user messages and summarizes AI actions and sub-agent outcomes. Summaries cached at ~/.claude/kaizen/session-summaries/.
100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific concrete actions, includes natural trigger phrases users would actually say, explicitly answers both what and when, and carves out a clear distinctive niche around Claude Code session history retrieval. The technical details (file paths, DuckDB, JSONL) add precision without becoming jargon-heavy.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Look up prior Claude Code sessions', 'Searches raw JSONL transcripts', 'Returns verbatim user messages', 'summarizes AI actions and sub-agent outcomes'. Also specifies technical details like DuckDB index and file paths. | 3 / 3 |
Completeness | Clearly answers both what (look up sessions, search transcripts, return messages, summarize actions) and when (explicit 'Use when' clause with multiple trigger phrases and scenarios). The when clause is comprehensive and explicit. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural phrases users would say: 'what did we do before?', 'what happened in the last session?', 'I forgot what we were working on', 'find what I told you about X', plus conceptual triggers like 'recall past conversation history, prior decisions, experiments, or outcomes'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on Claude Code session history lookup. The specific file paths (~/.claude/projects/, ~/.claude/kaizen/session-summaries/), technology (DuckDB, JSONL), and trigger phrases about 'last session' and 'prior decisions' make it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates strong technical writing. It provides concrete, executable commands with clear workflows, maintains token efficiency by avoiding unnecessary explanations, and organizes content logically from quick-start to detailed reference. The summary template and fidelity rules sections are particularly well-crafted for ensuring consistent, high-quality outputs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary information. No explanations of concepts Claude already knows (like what JSONL is or how DuckDB works). Every section earns its place with actionable content. | 3 / 3 |
Actionability | Fully executable commands throughout with copy-paste ready examples. The script invocations are concrete with real arguments, the summary template is complete and specific, and the JSONL schema reference provides exact field names and structures. | 3 / 3 |
Workflow Clarity | The 'I forgot what happened' workflow is clearly sequenced with numbered steps progressing from quick lookup to detailed summary generation. The fidelity rules section provides explicit validation guidance ('Read before summarizing', 'Verbatim user messages'). | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections: quick script reference at top, workflow for common use case, detailed command reference, and schema reference at bottom. Content is appropriately structured for a single-file skill without needing external references. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Jamie-BitFlight/claude_skills
- Commit
fd243f9
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.