Stats
Actions
Tags
From chronicle
Search every past Claude Code session and rehydrate any of them for /resume. Invoke when the user references prior work that isn't in your current context — "that thing we did with X", "resume the Y session", "find that conversation about Z" — instead of asking them to remind you. Also use to scope by callsign (`callsign:Frank`) or by project.
How this skill is triggered — by the user, by Claude, or both
Slash command
/chronicle:chronicleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You have access to every Claude Code session that was ever archived from `~/.claude/projects/` to the local vault. They're indexed by SQLite FTS5. Use `chronicle` instead of asking the user to refresh you on past work.
You have access to every Claude Code session that was ever archived from ~/.claude/projects/ to the local vault. They're indexed by SQLite FTS5. Use chronicle instead of asking the user to refresh you on past work.
chronicle recall "QUERY" --limit 5 --include-summary
recall returns JSON: ranked matches with summary text, project, timestamps, callsign, snippet, and a rehydrate_cmd per hit. Read the top match; if it answers the question, use it directly.
FTS5 syntax you can use:
| query | meaning |
|---|---|
wellrx foamer | both terms |
"FSC 600" | exact phrase |
foamer NEAR/5 pressure | within 5 tokens |
callsign:Frank | only Frank's sessions |
project_slug:wellrx | only wellrx project |
wellrx AND (chemistry OR diff) | boolean |
Just answering? Use summary and first_user_text from the recall result. Cite the uuid in your reply so the user can dig in if they want.
User wants to /resume? Rehydrate:
chronicle rehydrate <uuid>
Then tell the user:
"Session
<uuid>restored. Run/resume <uuid>to continue it."
Do not rehydrate eagerly — it adds a JSONL back to ~/.claude/projects/. Only do it when the user wants to actually resume.
chronicle context UUID # markdown context block, paste-into-prompt
chronicle show UUID --json # full metadata
chronicle list --project P # most-recent in a project
chronicle stats # vault totals
chronicle path # vault path + writability
0 ok · 1 partial · 2 vault unavailable · 3 invalid input · 4 uuid not found · 5 vault file missing.
On 2, the vault isn't mounted — surface to the user. On 4/5, re-search with different terms.
If you're MCP-enabled, the same operations are available as tools: chronicle_recall, chronicle_search, chronicle_show, chronicle_context, chronicle_list, chronicle_rehydrate, chronicle_stats, chronicle_agent_guide. Prefer MCP tools over shelling out when both are available.
Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.
npx claudepluginhub heyfinal/chronicle --plugin chronicle