wiki-history-ingest

Route agent-history ingestion requests to the correct wiki workflow.

4|Updated May 9, 2026

Search Tags:#routing #knowledge base #Obsidian #conversation memory #wiki-ingest #history ingestion #agent artifacts

Ready to run

npx skills add https://github.com/itsmarsss/memento --skill wiki-history-ingest-itsmarsss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wiki-history-ingest
Source: https://github.com/itsmarsss/memento/tree/main/obsidian-wiki/.cursor/skills/wiki-history-ingest
Command: npx skills add https://github.com/itsmarsss/memento --skill wiki-history-ingest-itsmarsss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the friction of figuring out which agent-history source (Claude, Copilot, Codex, Hermes, OpenClaw) a user has and ensures the correct ingestion workflow is selected for that history.

Core Features & Use Cases

Unified history router: Dispatches history-only ingestion to the correct underlying skill based on explicit target names or common filesystem/source patterns.
Source-aware routing: Infers the right destination skill from typical user directories and artifact formats such as agent memory/session JSONL or related databases.
Execution-contract enforcement: Ensures the destination skill’s workflow runs without duplicating ingest logic in the router.

Quick Start

Ask for history ingestion by saying: “/wiki-history-ingest claude”.

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 conversation history from local agent artifacts into a knowledge base?▼

Ingesting conversation history from local agent artifacts requires routing the session data to the correct wiki ingestion workflow. This skill automatically dispatches the ingestion request based on the agent source, such as Claude or Copilot, to process the history correctly.

What is the best way to route agent session JSONL files for Obsidian wiki ingestion?▼

Routing agent session JSONL files for Obsidian wiki ingestion is handled by inferring the correct destination workflow from filesystem paths or explicit subcommands. The router identifies the source format and executes the target skill's ingestion process without duplicating logic.

Can I ingest history from multiple sources like Claude, Copilot, Codex, Hermes, and OpenClaw?▼

You can ingest history from Claude, Copilot, Codex, Hermes, and OpenClaw sources. The router applies deterministic rules to identify the specific agent source from artifacts or explicit subcommands and then triggers the appropriate destination skill for that platform.

Do I need to specify the destination skill name when ingesting conversational memory?▼

You do not need to specify the destination skill name when ingesting conversational memory. The router uses explicit subcommand targets and filesystem inference rules to automatically determine and execute the correct underlying wiki ingestion workflow for your agent artifacts.

Why does my agent history ingestion workflow fail to route correctly?▼

Agent history ingestion routing fails when the source artifacts lack recognizable filesystem patterns or explicit subcommand targets. Ensure your agent memory or session JSONL files match expected directory structures so the router can successfully infer and dispatch to the correct destination workflow.