PluginBench
Skill
Pass
Audit score 90

wiki-history-ingest

ar9av/obsidian-wiki

Router for ingesting agent conversation history from Claude, Copilot, Codex, Hermes, OpenClaw, or Pi.

What is wiki-history-ingest?

A thin dispatcher that routes agent history ingestion requests to specialized skills based on the target agent. Use this when you need to import conversation sessions or memory artifacts from any supported AI agent into your wiki.

  • Routes history ingest requests to the correct agent-specific skill
  • Supports Claude, Copilot, Codex, Hermes, OpenClaw, and Pi history sources
  • Auto-detects agent type from file paths and session artifacts
  • Distinguishes between document ingestion (wiki-ingest) and history ingestion (wiki-history-ingest)
  • Delegates full workflow execution to destination skills

How to install wiki-history-ingest

npx skills add https://github.com/ar9av/obsidian-wiki --skill wiki-history-ingest
Claude Code
Cursor
Windsurf
Cline

How to use wiki-history-ingest

  1. 1.Invoke with `/wiki-history-ingest <agent-name>` where agent-name is claude, copilot, codex, hermes, openclaw, or pi
  2. 2.Alternatively provide a file path or session artifact; the skill will auto-detect the agent type
  3. 3.If ambiguous, respond to the clarification prompt selecting your target agent
  4. 4.The skill routes to the appropriate agent-specific history ingest skill and executes its workflow

Use cases

Good for
  • Import Claude conversation sessions from ~/.claude JSONL files
  • Ingest VS Code Copilot chat transcripts and session-store.db
  • Load Codex rollout/session index artifacts
  • Migrate Hermes agent memory and session data
  • Import OpenClaw MEMORY.md and session artifacts
Who it's for
  • AI agent users managing multiple conversation histories
  • Developers consolidating agent interactions into a unified wiki
  • Teams tracking agent-assisted coding sessions across platforms

wiki-history-ingest FAQ

What's the difference between wiki-ingest and wiki-history-ingest?

wiki-ingest is for documents and content sources. wiki-history-ingest is specifically for agent conversation history and session artifacts.

Can I use auto-detection instead of naming the agent?

Yes. Provide a file path or session artifact and the skill will infer the agent type using routing rules (e.g., ~/.claude for Claude, session-store.db for Copilot).

What happens after I invoke this skill?

The skill routes to the destination agent-specific skill and executes its complete workflow. Manifest, index, and log updates are handled by the destination skill.

Which agents are supported?

Claude, Copilot, Codex, Hermes, OpenClaw, and Pi.

Full instructions (SKILL.md)

Source of truth, from ar9av/obsidian-wiki.


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 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.

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:

SubcommandRoute To
claudeclaude-history-ingest
copilotcopilot-history-ingest
codexcodex-history-ingest
hermeshermes-history-ingest
openclawopenclaw-history-ingest
pipi-history-ingest
autoinfer 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