skills.rest
zjykzk
zjykzkCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

wiki-history-ingest

Route agent conversation histories to specialized history ingest skills.

Updated Feb 2, 2016
Search Tags:#workflow#routing#router#ai-skill#agent-history#history-ingest#wiki-history
One-click install
npx skills add https://github.com/zjykzk/blog --skill wiki-history-ingest-zjykzk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-history-ingest
Source: https://github.com/zjykzk/blog/tree/main/.agents/skills/wiki-history-ingest
Command: npx skills add https://github.com/zjykzk/blog --skill wiki-history-ingest-zjykzk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This router handles ingestion routing for agent history sources, directing them to the appropriate specialized history skill and avoiding document-focused ingestion.

Core Features & Use Cases

  • Routes to claude-history-ingest, copilot-history-ingest, codex-history-ingest, hermes-history-ingest, openclaw-history-ingest, or pi-history-ingest based on the user command or memory artifacts.
  • Defines routing rules for explicit mentions, artifact paths, and ambiguity clarifications.
  • Ensures execution of the selected destination skill without duplicating logic and preserves manifest/update semantics.

Quick Start

Invoke /wiki-history-ingest claude to route agent history to claude-history-ingest.

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 ingest workflow?▼

Agent conversation history is routed to the correct ingest workflow by applying explicit subcommand mapping rules that direct sources like Claude, Copilot, or generic histories to specialized skills without duplicating logic.

What is the best way to ingest Claude or Copilot conversation histories?▼

The best way to ingest Claude or Copilot histories is to use a unified router that applies explicit routing rules based on user commands or memory artifacts, directing them to their respective specialized history ingest skills.

Does wiki-history-ingest work with generic agent histories or only specific platforms?▼

Wiki-history-ingest works with both specific platforms like Claude, Copilot, Codex, Hermes, OpenClaw, and Pi, as well as generic agent histories, applying routing decisions based on explicit mentions and ambiguity clarifications.

How do I avoid document-focused ingestion when processing agent history?▼

To avoid document-focused ingestion during agent history processing, this router ensures inputs are directed exclusively to specialized history ingest skills, preserving manifest and update semantics for modular routing.

What routing rules apply when agent history sources are ambiguous?▼

When agent history sources are ambiguous, routing rules apply ambiguity clarifications to ensure the correct specialized history skill is selected, satisfying the execution contracts required by the history-ingest workflow.

Related Skills

Explore More Software Engineering Skills→
Abulfadl-AhmadiAbulfadl-Ahmadi

wiki-history-ingest

Route history ingestion from Claude, Copilot, Codex, Hermes, OpenClaw, and Pi agents.

Community
Intermediate
pax-kpax-k
6

wiki-history-ingest

Route history ingestion commands to specialized history skills.

Community
Intermediate
Ar9avAr9av
3.2k

wiki-history-ingest

Route wiki history sources to the appropriate specialized ingest skill.

Community
Intermediate
OmarHosamCodesOmarHosamCodes
1

wiki-history-ingest

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

Community
Intermediate