Wiki History Ingest

---
name: wiki-history-ingest
description: >
  Unified wiki-history-ingest entrypoint for conversation/session sources. Use this when the user says
  "/wiki-history-ingest claude", "/wiki-history-ingest hermes", or asks to ingest agent history
  without naming the underlying skill. This router dispatches to the specialized history skill.
---

# 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` |
| `hermes` | `hermes-history-ingest` |
| `auto` | infer from context using rules below |

## Routing Rules

1. If the user explicitly says `claude` or `hermes`, route directly.
2. If the user provides a path/source:
   - `~/.claude` or Claude memory/session JSONL artifacts -> `claude-history-ingest`
   - `~/.hermes`, `HERMES_HOME`, or Hermes memories/session artifacts -> `hermes-history-ingest`
3. If ambiguous, ask one short clarification:
   - "Should I ingest `claude` or `hermes` history?"
4. If the user names an agent with no matching skill installed (e.g. `copilot`, `codex`,
   `openclaw`, `pi`), say the corresponding history-ingest skill is not installed and fall
   back to `wiki-ingest` on the raw export files instead.

## 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 hermes`
- `$wiki-history-ingest claude` (agents that use `$skill` invocation)