Unified wiki-history-ingest entrypoint for conversation/session sources. Use this when the user says "/wiki-history-ingest claude" or "/wiki-history-ingest codex", or asks to ingest agent history without naming the underlying skill. This router dispatches to the specialized history 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 |
codex | codex-history-ingest |
auto | infer from context using rules below |
claude or codex, route directly.~/.claude or Claude memory/session JSONL artifacts -> claude-history-ingest~/.codex or rollout/session index artifacts -> codex-history-ingestclaude or codex history?"claude and codex history ingesters are installed in this repository.wiki-ingest for documents/content sourceswiki-history-ingest for agent history sourcesExamples:
/wiki-history-ingest claude/wiki-history-ingest codex$wiki-history-ingest claude (agents that use $skill invocation)saski/arnesto
752f690
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.