wiki-history-ingest

Route agent-history sources to specialized history-ingest skills by target or artifact context.

1|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/OmarHosamCodes/brainiac --skill wiki-history-ingest-omarhosamcodes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-history-ingest
Source: https://github.com/OmarHosamCodes/brainiac/tree/main/.agents/skills/wiki-history-ingest
Command: npx skills add https://github.com/OmarHosamCodes/brainiac --skill wiki-history-ingest-omarhosamcodes

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

  • Directly routes to claude-history-ingest, codex-history-ingest, hermes-history-ingest, or openclaw-history-ingest based on explicit targets.
  • Routes based on artifact cues such as memory or session artifacts like ~/.claude, ~/.codex, ~/.hermes, or ~/.openclaw to select the correct history-ingest skill.
  • Preserves existing wiki-ingest behavior for document ingestion by not replacing document routing.

Quick Start

Invoke the router with a target such as /wiki-history-ingest claude to route to the claude-history-ingest skill.

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 conversation history to the correct ingestion skill?▼

Agent conversation history routing uses explicit targets like claude or codex to dispatch to the matching specialized history-ingest skill. The router evaluates invocation arguments and delegates updates without duplicating destination logic.

Can I automatically select a history ingestion skill based on artifact cues?▼

Artifact cues like ~/.claude, ~/.codex, ~/.hermes, or ~/.openclaw directories drive automatic routing to the correct history-ingest skill. The router detects these session artifacts and selects the specialized ingestion target.

What is the best way to ingest agent history without naming the underlying skill?▼

Ingesting agent history without naming the underlying skill requires invoking the wiki-history-ingest router with a target such as claude. The router dispatches the request to the appropriate specialized ingestion skill deterministically.

Does routing agent history conflict with existing document ingestion workflows?▼

Routing agent history does not conflict with document ingestion workflows. The router preserves existing wiki-ingest behavior for documents and only applies deterministic routing rules to conversation and session ingestion scenarios.

Why use a dedicated router for session history instead of calling specialized skills directly?▼

A dedicated router for session history provides a unified entrypoint and deterministic routing based on explicit targets or artifact context. It delegates updates to the selected history-ingest skill without duplicating destination logic across workflows.

What agent history targets are supported for ingestion routing?▼

Agent history ingestion routing supports explicit targets including claude, codex, hermes, and openclaw. The router dispatches to the matching specialized history-ingest skill based on these named targets or detected artifact cues.