Route generic agent-history ingestion requests to the appropriate specialized history-ingest skill. Use when the user asks to ingest AI-agent history without directly selecting the underlying agent-specific skill.
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
This is a thin router for history sources only. It does not replace wiki-ingest for documents.
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 |
claude, copilot, codex, hermes, openclaw, or pi, route directly.~/.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-ingestclaude, copilot, codex, hermes, openclaw, or pi history?"wiki-ingest for documents/content sourceswiki-history-ingest for agent history sourcesExamples:
/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 copilotAr9av/obsidian-wiki
4f457e1
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.