Agent skill · Security

claude-history-ingest

Ingest Claude Code conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Claude conversations for knowledge, import their ~/.claude folder, extract insights from previous coding sessions, or says things like "process my Claude history", "add my conversations to the wiki", "what have I discussed with Claude before". Also triggers when the user mentions their .claude folder, Claude projects, session data, past conversation logs, local-agent-mode sessions, or audit logs.

Ar9avgithub.com/Ar9avGitHub ↗
claude-codeMIT
Install
npx skills add Ar9av/obsidian-wiki --skill claude-history-ingest --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 21 KB
Bundled scripts: none
Path: .skills/claude-history-ingest/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 3,115
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

Ingest Claude Code conversation history into the Obsidian wiki. It extracts knowledge from past Claude conversations, imports the ~/.claude folder, and distills it into wiki pages. It supports pre-extraction to reduce noise, then parses extracted conversations or raw JSONL, and can integrate memory files and audit logs to build topic-based wiki content per project. It can be invoked directly or via the router /wiki-history-ingest claude.

How it works

  • Resolve configuration to obtain OBSIDIAN_VAULT_PATH and CLAUDE_HISTORY_PATH, reading manifest and index to understand existing content.
  • Determine projects to process and skip any whose names match WIKI_SKIP_PROJECTS. Apply exclusion uniformly across all steps.
  • Ingest in modes (Append by default, Full if requested):
    • If Append: process files not in manifest or newer than ingested_at, using canonical paths and a manifest helper to avoid re-ingesting
    • Pre-extraction (recommended): run scripts/extract-jsonl.py to generate compact JSON in ~/.claude/extracted/, reducing token usage
    • Parse conversations from ~/.claude/projects/*/*.jsonl preferentially using extracted JSONs if present; otherwise fall back to raw JSONL
    • If using desktop data: parse audit.jsonl for detailed tool calls and actions, combined with session metadata in local_<uuid>.json to provide context
    • Use memory files in memory/*.md as pre-distilled signals and propagate their types (user, feedback, project, reference) into the wiki
  • Step 3b (desktop only): integrate audit logs with session metadata to contextualize actions and identify patterns
  • Step 4: Cluster knowledge by topic across conversations, not one page per conversation
  • Step 5: Distill into wiki pages per Claude project, decoding path-encoded project names to clean project names and organize the vault accordingly

When to use it

Triggers when the user asks to process Claude history or mentions the .claude folder, Claude projects, session data, past conversation logs, or audit logs. Also usable via the wiki-history-ingest router.

What it can touch

  • Reads: ~/.claude/, ~/.claude/projects/*/memory/*.md, ~/.claude/projects/*/*.jsonl, ~/.claude/extracted/*/*.json, session metadata files, audit.jsonl in desktop sessions
  • Writes: wiki pages under the vault corresponding to each Claude project; updates and creates topic-based pages and references

Caveats

  • Requires configuration resolution to locate vault and Claude history paths
  • Relies on manifest to determine delta; may re-scan if paths are canonicalized differently
  • Pre-extraction reduces token usage but may skip some raw data unless fallback is used
  • The skill describes grouping by topic rather than one page per conversation; volume may affect page granularity
From the SKILL.md

# Claude History Ingest — Conversation Mining You are extracting knowledge from the user's past Claude Code conversations and distilling it into the Obsidian wiki. Conversations are rich but messy — your job is to find the signal and compile it. This skill can be invoked directly or via the `wiki-history-ingest` router (`/wiki-history-ingest claude`). ## Before You Start 1. **Resolve config** — fo

More from obsidian-wiki
All skills →
About this skill
What does the claude-history-ingest skill do?

Ingest Claude Code conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Claude conversations for knowledge, import their ~/.claude folder, extract insights from previous coding sessions, or says things like "process my Claude history", "add my conversations to the wiki", "what have I discussed with Claude before". Also triggers when the user mentions their .claude folder, Claude projects, session data, past conversation logs, local-agent-mode sessions, or audit logs.

How do I install it?

Run `npx skills add Ar9av/obsidian-wiki --skill claude-history-ingest --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Ar9av/obsidian-wiki, a repository with 3,115 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going