Wiki History Ingest
Route a single /wiki-history-ingest command to the right Claude, Copilot, Codex, Pi, or other agent history ingester so sessions land in your Obsidian wiki without remembering per-agent skill names.
Install
npx skills add https://github.com/ar9av/obsidian-wiki --skill wiki-history-ingestWhat is this skill?
- Thin router entrypoint: does not replace wiki-ingest for arbitrary documents
- Explicit subcommands: claude, copilot, codex, hermes, openclaw, pi, and auto inference
- Path-based routing rules for ~/.claude, ~/.copilot, ~/.codex, ~/.hermes, ~/.openclaw, and Pi artifacts
- Dispatches to specialized skills such as claude-history-ingest and codex-history-ingest
- Auto mode infers target from user context when no subcommand is named
Adoption & trust: 2.1k installs on skills.sh; 1.8k GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Grill Memattpocock/skills
Grill With Docsmattpocock/skills
Brainstormingobra/superpowers
Lark Tasklarksuite/cli
Lark Workflow Standup Reportlarksuite/cli
Cavemanjuliusbrussee/blueprint
Journey fit
Primary fit
Operate/iterate is the canonical shelf because the skill turns past agent sessions into durable wiki knowledge you reuse while running and improving your product. Iterate fits ongoing capture of conversation artifacts into a personal knowledge base rather than one-off document import.
Common Questions / FAQ
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.
SKILL.md
READMESKILL.md - Wiki History Ingest
# 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: - `~/.claude` or Claude memory/session JSONL artifacts -> `claude-history-ingest` - `~/.copilot`, `session-store.db`, VS Code copilot-chat transcripts -> `copilot-history-ingest` - `~/.codex` or rollout/session index artifacts -> `codex-history-ingest` - `~/.hermes` or Hermes memories/session artifacts -> `hermes-history-ingest` - `~/.openclaw` or OpenClaw MEMORY.md/session JSONL artifacts -> `openclaw-history-ingest` - `~/.pi/agent/sessions` or Pi session JSONL artifacts -> `pi-history-ingest` 3. If ambiguous, ask one short clarification: - "Should I ingest `claude`, `copilot`, `codex`, `hermes`, `openclaw`, or `pi` history?" ## 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-ingest` for **documents/content sources** - Use `wiki-history-ingest` for **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 `$skill` invocation) - `$wiki-history-ingest copilot`