skills.rest
Michael1Peng
Michael1PengCOMMUNITY
Explore all skills by this author →
GitHub

wiki-history-ingest

Route agent history ingestion requests to the appropriate specialized ingester.

Updated Aug 27, 2026
Search Tags:#routing#agents#dispatch#ingestion#wiki#route#history-ingest
One-click install
npx skills add https://github.com/Michael1Peng/watson --skill wiki-history-ingest-michael1peng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-history-ingest
Source: https://github.com/Michael1Peng/watson/tree/main/.agents/skills/wiki-history-ingest
Command: npx skills add https://github.com/Michael1Peng/watson --skill wiki-history-ingest-michael1peng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This router solves the problem of routing agent history ingestion requests to the correct specialized history skill, ensuring consistent routing and avoiding manual selection.

Core Features & Use Cases

  • Directs /wiki-history-ingest claude to claude-history-ingest
  • Dispatches to codex-history-ingest, hermes-history-ingest, or openclaw-history-ingest based on explicit targets or context
  • Prompts for clarification when input is ambiguous to prevent misrouting

Quick Start

Use the router to dispatch a history-ingest request, for example '/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 route agent history ingestion requests to the correct specialized skill?▼

Agent history ingestion routing is handled by dispatching requests to specialized ingesters based on explicit targets like claude, codex, hermes, or openclaw, or by auto-routing based on source context.

What happens when an agent history ingest command is ambiguous?▼

When agent history ingestion input is ambiguous, the router prompts for clarification to prevent misrouting and ensures the request is delegated to the correct specialized history ingester.

Can I auto-route history ingestion without manually specifying the target agent?▼

Yes, history ingestion auto-routing works by detecting the source context and delegating the request to the appropriate specialized ingester without requiring a manually specified target.

How do I dispatch a wiki history ingest request for a specific agent?▼

Wiki history ingest dispatching is initiated by using the router command followed by the target agent name, such as '/wiki-history-ingest claude', which directs the request to the claude-history-ingest skill.

Does the history ingestion router duplicate the logic of the specialized ingesters it dispatches to?▼

No, the history ingestion router delegates to the destination skill without duplicating logic, acting purely as a unified routing layer for consistent agent history ingestion.

When should I use a unified router instead of calling a specialized history ingester directly?▼

Use a unified history ingestion router when you need consistent routing across multiple agent sources and want to avoid manually selecting the correct specialized history skill.

Related Skills

Explore More Software Engineering Skills→
Ar9avAr9av
3.2k

wiki-history-ingest

Route wiki history sources to the appropriate specialized ingest skill.

Community
Intermediate
NehoraiHadadNehoraiHadad

maestro-delegation-advisor

Route tasks to Claude, Codex, or Gemini based on agent strengths.

Community
Advanced
pax-kpax-k
6

wiki-history-ingest

Route history ingestion commands to specialized history skills.

Community
Intermediate
NirajkashyapNirajkashyap

wiki-history-ingest

Route agent history sources to the appropriate history-ingest workflow.

Community
Intermediate