history

Skill: History

Purpose

Browse and search past analyses from the analysis archive. Helps users recall what they've analyzed before, find prior findings, and build on previous work.

When to Use

• User says /history or "what have I analyzed before?"
• At session start, to provide context on prior work
• When framing a new question, to check if similar analysis exists

Invocation

/history — list recent analyses (last 10) /history {id} — show full details for a specific analysis /history search={term} — search by title, question, or tags /history --all — list all analyses across all datasets /history dataset={id} — filter to a specific dataset

Instructions

Step 1: Load Archive

1. Read .knowledge/analyses/index.yaml
2. If empty: "No analyses archived yet. Complete an analysis and it will appear here."

Step 2: Determine Active Dataset (Critical)

IMPORTANT: Before filtering results, determine the active dataset:

1. Read .knowledge/active.yaml to get the active dataset ID
2. If --all flag is present: skip filtering, show all datasets
3. If dataset={id} is specified: filter to that dataset
4. Otherwise: filter to active dataset only

This ensures users see relevant analyses for their current working context by default.

Step 3: Execute Command

List recent (/history):

• Filter to active dataset (unless --all flag present)
• Sort by date descending
• Show last 10 as a table: date, title, level, key finding count, dataset
• Show total count: "Showing 10 of {total} analyses for {dataset_name}." (or "across all datasets" if --all)

Show specific (/history {id}):

• Find entry by ID in index
• Display: title, date, question, level, all key findings, metrics used, agents used, output files, tags, confidence, recommendations
• If output files exist, offer: "Want to review the full analysis? The deck is at {path}"

Search (/history search={term}):

• Filter to active dataset first (unless --all or dataset={id} specified)
• Search across: title, question, key_findings, tags (case-insensitive)
• Display matching entries as a table
• If no matches: "No analyses match '{term}' in {dataset_name}. Try broader terms or use --all to search across all datasets."