Unified History Ingest Router
SkillDocs & knowledgeLets your agent turn saved chat histories from tools like Claude or Copilot into wiki pages in Obsidian.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Unified History Ingest Router skill
About this capability
Unified wiki-history-ingest entrypoint for conversation/session sources. Use this when the user says "/wiki-history-ingest claude", "/wiki-history-ingest copilot", "/wiki-history-ingest codex", "/wiki-history-ingest pi", or asks to ingest agent history without naming the underlying skill. This route
What this skill tells your AI
The instructions your AI receives, as published by ar9av/obsidian-wiki in .skills/wiki-history-ingest/SKILL.md and read by ahel’s review.
This is a thin router for history sources only. It does not replace wiki-ingest for documents.
Subcommands
If the user invokes /wiki-history-ingest <target> (or equivalent text command), dispatch directly:
| Subcommand | Route To |
|---|---|
claude | claude-history-ingest |
copilot | copilot-history-ingest |
codex | codex-history-ingest |
hermes | hermes-history-ingest |
openclaw | openclaw-history-ingest |
pi | pi-history-ingest |
auto | infer from context using rules below |
Routing Rules
- If the user explicitly says
claude,copilot,codex,hermes,openclaw, orpi, route directly. - If the user provides a path/source:
~/.claudeor Claude memory/session JSONL artifacts ->claude-history-ingest~/.copilot,session-store.db, VS Code copilot-chat transcripts ->copilot-history-ingest~/.codexor rollout/session index artifacts ->codex-history-ingest~/.hermesor Hermes memories/session artifacts ->hermes-history-ingest~/.openclawor OpenClaw MEMORY.md/session JSONL artifacts ->openclaw-history-ingest~/.pi/agent/sessionsor Pi session JSONL artifacts ->pi-history-ingest
- If ambiguous, ask one short clarification:
- "Should I ingest
claude,copilot,codex,hermes,openclaw, orpihistory?"
- "Should I ingest
Execution Contract
- After routing, execute the destination skill's workflow exactly.
- Do not duplicate destination logic in this file.
- Leave manifest/index/log update semantics to the destination skill.
UX Convention
- Use
wiki-ingestfor documents/content sources - Use
wiki-history-ingestfor agent history sources
Examples:
/wiki-history-ingest claude/wiki-history-ingest copilot/wiki-history-ingest codex/wiki-history-ingest hermes/wiki-history-ingest openclaw/wiki-history-ingest pi$wiki-history-ingest claude(agents that use$skillinvocation)$wiki-history-ingest copilot
Signals
- GitHub stars
- 3k
- Forks
- 338
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
wiki-history-ingest- Source
- github.com/ar9av/obsidian-wiki