wiki-history-ingest

Route agent history sources to specialized ingesters for Claude, Codex, Hermes, and OpenClaw.

Updated Aug 27, 2026

Search Tags:#routing #codex #claude #dispatch #agent-history #history-ingest #wiki-history

Ready to run

npx skills add https://github.com/samuelcastro/noter --skill wiki-history-ingest-samuelcastro

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wiki-history-ingest
Source: https://github.com/samuelcastro/noter/tree/main/.agents/skills/wiki-history-ingest
Command: npx skills add https://github.com/samuelcastro/noter --skill wiki-history-ingest-samuelcastro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified wiki-history-ingest entrypoint for conversation and 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.

Core Features & Use Cases

Thin router for history sources only; it does not replace wiki-ingest for documents.
Dispatches to specialized history ingests (claude-history-ingest, codex-history-ingest, hermes-history-ingest, openclaw-history-ingest) or auto inference based on context.
Execution contract: After routing, it delegates to the destination skill's workflow without duplicating destination logic.

Quick Start

Invoke the router with a target history source to route and ingest the specified agent history.

Frequently Asked Questions about wiki-history-ingest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I route agent history from multiple sources like Claude and Codex for ingestion?▼

Agent history routing dispatches sources from Claude, Codex, Hermes, and OpenClaw to specialized history ingesters. The router delegates execution to the destination skill without duplicating logic, preserving routing rules and context throughout the ingestion process.

What is the difference between wiki-history-ingest and a general wiki document ingest?▼

Wiki-history-ingest is a thin router specifically for conversation and session history sources, not general documents. It handles agent history exclusively and delegates to specialized history ingesters, whereas wiki-ingest covers broader document ingestion tasks.

Can I auto-infer the correct history ingester without explicitly naming the source?▼

Yes, the router supports auto inference based on context. When you ask to ingest agent history without naming the underlying skill, it determines the appropriate destination history ingester automatically and dispatches accordingly.

Do I need separate skills installed to ingest Claude or Codex conversation logs?▼

The router delegates to specialized destination skills such as claude-history-ingest, codex-history-ingest, hermes-history-ingest, and openclaw-history-ingest. It acts as an entrypoint that dispatches without duplicating the destination ingester logic.

How do I start ingesting agent history using the wiki-history-ingest router?▼

Invoke the router with a target history source by saying "/wiki-history-ingest claude" or "/wiki-history-ingest codex". The router then dispatches to the specialized history ingester for that source to complete the workflow.

When should I avoid using a router for agent history ingestion?▼

You should not use this router for general document ingestion, as it is a thin router for history sources only. It does not replace wiki-ingest for documents and is limited to dispatching conversation and session history to specialized ingesters.