kestrel-mcp

Route agent intents to specialized sub-skills within the Kestrel-MCP workspace.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Srain021/KesTREL --skill kestrel-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kestrel-mcp
Source: https://github.com/Srain021/KesTREL/tree/main/.cursor/skills-cursor/kestrel-mcp
Command: npx skills add https://github.com/Srain021/KesTREL --skill kestrel-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates and routes user intents to the correct specialized Skill Units within the Kestrel-MCP workspace, enabling safe, modular execution of complex RFC workflows.

Core Features & Use Cases

  • Intent routing: Directs triggers like "run RFC-001" or "bootstrap" to the appropriate sub-skills (bootstrap, exec, plan, audit, handoff, query, health, roles, team).
  • Safety & scoping: Enforces project-wide safety checks and dependencies before delegation to a sub-skill.
  • Governance routing: Serves as the single-entry point for map RFCs to their execution and validation workflows.

Quick Start

Use the kestrel-mcp root skill to route a user session toward bootstrap/ or exec/rfc/ based on the user's trigger phrase.

Frequently Asked Questions about kestrel-mcp

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

FAQPage Schema
How do I route agent intents to specialized sub-skills for execution?

Agent intent routing directs user triggers like "run RFC-001" to appropriate sub-skills within the Kestrel-MCP workspace for execution. It enforces project-wide safety checks and dependencies before delegating work to bootstrap, exec, plan, or audit skills.

What is MCP governance routing and when do I need it for agent workflows?

MCP governance routing maps RFCs to their execution and validation workflows via a single entry point. You need it when orchestrating complex agent workflows that require consistent scope enforcement, budget constraints, and safe delegation to specialized modular skills.

How to enforce scope and budget constraints when delegating tasks to agent sub-skills?

Enforce scope and budget constraints by routing only allowed actions to downstream RFCs and audits. The root skill acts as a discovery-driven entrypoint, performing safety checks before delegating triggers to exec, plan, or handoff sub-skills.

Does Kestrel-MCP support bootstrap and execution workflows for new agent sessions?

Kestrel-MCP supports both bootstrap and execution workflows by routing user trigger phrases to the appropriate sub-skills. A session trigger like "bootstrap" directs the agent to initialization skills, while execution triggers map to exec or plan workflows.

Can I use trigger phrases to map RFCs to validation and audit workflows?

You can use trigger phrases to map RFCs to validation and audit workflows. The root skill recognizes specific triggers and routes them to dedicated sub-skills like audit, query, health, and roles for execution and governance validation.

What are the limitations of using a single entry point for agent workflow orchestration?

The single entry point limits direct access to sub-skills, requiring all intents to pass through governance routing. This ensures safe delegation but means triggers must match expected phrases to correctly route to bootstrap, exec, plan, audit, or handoff skills.