wiki-history-ingest

Routes agent history ingestion requests to specialized source-specific skills.

Updated Nov 9, 2023
One-click install
npx skills add https://github.com/oresttokovenko/dot-files --skill wiki-history-ingest-oresttokovenko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-history-ingest
Source: https://github.com/oresttokovenko/dot-files/tree/main/chezmoi/dot_agents/skills/wiki-history-ingest
Command: npx skills add https://github.com/oresttokovenko/dot-files --skill wiki-history-ingest-oresttokovenko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you want to ingest conversation or session history from an AI agent into your wiki but cannot remember which specialized skill handles your source, this router removes the guesswork by dispatching your request to the correct history-ingest skill automatically. ## Core Features & Use Cases - Unified Entrypoint: Accepts a single /wiki-history-ingest <target> command for claude, copilot, codex, hermes, openclaw, and pi history sources. - Path-Based Inference: Detects the correct destination skill from artifacts like ~/.claude session JSONL files, session-store.db, or ~/.codex rollout indexes. - Ambiguity Handling: Asks one short clarifying question when the source cannot be determined from context. - Use Case: You run /wiki-history-ingest copilot and the router hands off execution to the copilot-history-ingest skill, which performs the actual manifest, index, and log updates. ## Quick Start Ask the assistant to run /wiki-history-ingest claude to ingest your Claude session history into the wiki.

Frequently Asked Questions about wiki-history-ingest

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

FAQPage Schema
How do I ingest Claude session history into my wiki?

Run /wiki-history-ingest claude and the router dispatches to the claude-history-ingest skill, which processes Claude memory and session JSONL artifacts from ~/.claude. The destination skill handles all manifest, index, and log updates.

What is the difference between wiki-ingest and wiki-history-ingest?

wiki-ingest handles documents and general content sources, while wiki-history-ingest handles agent conversation and session history sources. Use the history router only for transcripts from Claude, Copilot, Codex, Hermes, OpenClaw, or Pi.

Which agent history sources does wiki-history-ingest support?

It supports six sources: claude, copilot, codex, hermes, openclaw, and pi. Each subcommand routes to a dedicated skill such as copilot-history-ingest or pi-history-ingest that executes the actual ingestion workflow.

Can wiki-history-ingest detect the source automatically?

Yes, the auto subcommand infers the source from provided paths or artifacts, such as ~/.copilot, session-store.db, or Pi session JSONL files. If the source remains ambiguous, it asks one short clarifying question before routing.

Does wiki-history-ingest perform the ingestion itself?

No, it is a thin router that only dispatches to the destination skill. All ingestion logic, manifest updates, and index maintenance are executed by the specialized history skill it routes to.