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 router dispatches to the specialized history skill.
SkillScore100Maintained
Automatic
◆Knowledge Management pack
Last verified 8/12/2026
What it changes
Passed 22 of 22 test cases with the skill, and 4 of 22 without it.
Without skill18%
With skill100%
Checks it passed that the model alone missed
Routes to hermes-history-ingest
Routes to copilot-history-ingest
Routes the request to pi-history-ingest
and 14 more in the full report
18 fixed4 passed either way0 still failing0 broke
Pass-rate lift
+82 pp
Tokens
-26%
Agent turns
0%
Response time
-69%
Model gemini-3.6-flashMeasured 8/12/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 18
Prompt
Forward my history import command `/wiki-history-ingest hermes` to the target handler.
What was checked, without and with the skill
Checked
Without skill
With skill
Dispatches directly to hermes-history-ingest
Missed
Passed
case-07 · gemini-3.6-flash · 8/12/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md52 linessingle file
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
If the user explicitly says claude, copilot, codex, hermes, openclaw, or pi, route directly.
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
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.