Install
Use with your agent
Install the wiki-history-ingest skill, then use it as build context. Run: npx skills add https://github.com/ar9av/obsidian-wiki --skill wiki-history-ingest. Then read the installed skill.md and follow its guidance to build or refactor my project.
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 |
auto | infer from context using rules below |
Routing Rules
- If the user explicitly says
claude,copilot,codex,hermes, oropenclaw, 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
- If ambiguous, ask one short clarification:
- "Should I ingest
claude,copilot,codex,hermes, oropenclawhistory?"
- "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 claude(agents that use$skillinvocation)$wiki-history-ingest copilot