context-router

Route context extraction requests to CLI tools via triggers or intent signals.

7|3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Zpankz/mcp-skillset --skill context-router-zpankz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-router
Source: https://github.com/Zpankz/mcp-skillset/tree/main/context-router
Command: npx skills add https://github.com/Zpankz/mcp-skillset --skill context-router-zpankz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routes context extraction requests to the appropriate CLI tools, reducing manual routing and latency.

Core Features & Use Cases

  • Explicit routing: /context, /limitless, /research, /pieces direct requests to the correct sources.
  • Hook-based routing: Responds to intent signals to selectively gather context from personal, research, or local data.
  • Augmented & parallel modes: Supports single, parallel, and augmented extraction workflows for complex analyses.

Quick Start

Ask the Context Router to route your current inquiry to the appropriate sources using /context.

Frequently Asked Questions about context-router

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

FAQPage Schema
How do I route context extraction requests to different CLI tools automatically?

Route context extraction to specific CLI tools by using explicit triggers like /context or hook-based intent signals. This directs your inquiry to personal, research, or local data sources automatically.

What is the best way to gather context from multiple sources in parallel?

Gather context from multiple sources in parallel using augmented extraction modes. This supports complex analyses by routing requests simultaneously across varied workflows instead of querying each source manually.

Can I use intent signals to trigger context routing instead of explicit commands?

Yes, you can use hook-based routing to trigger context routing via intent signals. This selectively gathers context from personal, research, or local data without requiring explicit commands.

Does context routing support extracting data from local sources and research data simultaneously?

Yes, context routing supports extracting data from local and research sources simultaneously. It defines trigger conditions and source mappings for parallel and augmented modes to enable adaptable workflows.

Why use deterministic context routing instead of manual CLI tool selection?

Deterministic context routing reduces manual routing effort and latency. By defining explicit trigger conditions and source mappings, it ensures extraction requests consistently reach the correct CLI tools.