Wiki History Ingest
- 2.8k installs
- 3.1k repo stars
- Updated August 4, 2026
- ar9av/obsidian-wiki
wiki-history-ingest is an agent skill router that dispatches unified history ingest commands to claude, copilot, codex, hermes, openclaw, or pi specialized ingest skills.
About
wiki-history-ingest is a thin unified router for conversation and session history sources in the obsidian-wiki skill family. It does not replace wiki-ingest for documents; instead it dispatches explicit subcommands such as claude, copilot, codex, hermes, openclaw, or pi to their specialized history-ingest skills. Routing rules map filesystem paths like ~/.claude, ~/.copilot session-store.db, ~/.codex rollout artifacts, ~/.hermes memories, ~/.openclaw MEMORY.md files, and ~/.pi/agent/sessions JSONL to the correct destination skill. An auto subcommand infers the target from context using the same path rules when the user does not name an agent explicitly. When the target is ambiguous the router asks one short clarification question listing the supported agents. After routing it executes the destination workflow exactly without duplicating ingest logic, leaving manifest, index, and log updates to the specialized skill. UX convention separates wiki-ingest for document content sources from wiki-history-ingest for agent history sources.
- Routes claude copilot codex hermes openclaw and pi subcommands to specialized skills.
- Infers destination from known history paths like ~/.claude or ~/.codex artifacts.
- Does not duplicate destination ingest logic or manifest update semantics.
- Asks one clarification when the history source target is ambiguous.
- Complements wiki-ingest which handles document and content sources only.
Wiki History Ingest by the numbers
- 2,849 all-time installs (skills.sh)
- +30 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #144 of 1,879 Documentation skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
wiki-history-ingest capabilities & compatibility
- Capabilities
- subcommand routing to six history ingest skills · path based inference for claude copilot codex pi · single question ambiguity clarification
- Works with
- obsidian
- Use cases
- documentation · orchestration
What wiki-history-ingest says it does
After routing, execute the destination skill's workflow exactly.
npx skills add https://github.com/ar9av/obsidian-wiki --skill wiki-history-ingestAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.8k |
|---|---|
| repo stars | ★ 3.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | ar9av/obsidian-wiki ↗ |
Which obsidian-wiki history ingest skill should run when the user wants agent conversation history imported without naming the source explicitly?
Route wiki-history-ingest requests to the correct agent history ingest skill for Claude, Copilot, Codex, Hermes, OpenClaw, or Pi sources.
Who is it for?
Developers using obsidian-wiki who invoke /wiki-history-ingest with agent names or ambiguous history paths.
Skip if: Skip for document or markdown file ingestion; use wiki-ingest for content sources instead.
When should I use this skill?
User says /wiki-history-ingest claude, copilot, codex, pi, or asks to ingest agent history without naming the underlying skill.
What you get
Correct specialized history-ingest skill selected and executed with its native manifest and log update workflow.
- routed ingest execution
- Obsidian wiki pages from sessions
By the numbers
- Routes 4 agent history subcommands: claude, copilot, codex, and pi
Files
Unified History Ingest Router
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
1. If the user explicitly says claude, copilot, codex, hermes, openclaw, or pi, route directly. 2. 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
3. If ambiguous, ask one short clarification:
- "Should I ingest
claude,copilot,codex,hermes,openclaw, orpihistory?"
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
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71How it compares
History ingest router only; destination skills own the actual session parsing work.
FAQ
Does wiki-history-ingest process history itself?
No. It routes to specialized skills and executes their workflows without duplicating ingest logic.
When should I use wiki-ingest instead?
Use wiki-ingest for documents and content sources; wiki-history-ingest is for agent conversation history only.
Is Wiki History Ingest safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.