playbooks

home / skills / zpankz / mcp-skillset / infrastructure-router

infrastructure-router skill

/infrastructure-router

This skill routes infrastructure and MCP tasks, enabling seamless orchestration and tooling with clear decision routing for server, hooks, and pipelines.

npx playbooks add skill zpankz/mcp-skillset --skill infrastructure-router

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
2.0 KB
---
name: infrastructure-router
description: Routes infrastructure, MCP, and tooling tasks. Triggers on mcp, server, deploy, orchestrate, pipeline, tools, docker, ci/cd, hook, config, setup.
---

# Infrastructure Router

Routes infrastructure, MCP development, and tooling tasks.

## Subcategories

### MCP Development
```yaml
triggers: [mcp, model-context-protocol, server, tool-registration]
skills:
  - mcp-builder: MCP server development guide
  - component: Claude Code components
```

### Tooling / CLI
```yaml
triggers: [cli, tool, script, automation, batch]
skills:
  - terminal: Terminal UI design
  - ccs: Claude Code Spawner delegation
  - ccs-delegation: Auto-delegation patterns
```

### Hooks / Configuration
```yaml
triggers: [hook, config, setup, settings, plugin]
skills:
  - hookify: Hook creation from behaviors
  - component: Component generation
```

### Orchestration
```yaml
triggers: [orchestrate, pipeline, workflow, multi-agent, coordinate]
skills:
  - agent: Agentic reasoning framework
  - mcp-skillset-workflows: Multi-skill orchestration
```

## Routing Decision Tree

```
infrastructure request
    │
    ├── MCP development?
    │   ├── Server creation? → mcp-builder
    │   └── Component? → component
    │
    ├── CLI/Tooling?
    │   ├── Terminal UI? → terminal
    │   └── Delegation? → ccs
    │
    ├── Hooks/Config?
    │   ├── Hook creation? → hookify
    │   └── Settings? → component
    │
    └── Orchestration?
        ├── Multi-agent? → agent
        └── Workflows → mcp-skillset-workflows
```

## Managed Skills

| Skill | Purpose | Trigger |
|-------|---------|---------|
| mcp-builder | MCP server guide | "MCP", "server" |
| component | CC components | "command", "agent" |
| terminal | TUI design | "terminal", "CLI" |
| ccs | Claude spawner | "delegate", "spawn" |
| hookify | Hook creation | "hook", "prevent" |
| agent | Agentic framework | "orchestrate", "agent" |

Overview

This skill routes infrastructure, MCP development, and tooling tasks to the appropriate helper skills. It inspects request intent for keywords like mcp, server, deploy, cli, hook, orchestrate, pipeline, docker, and ci/cd and forwards the task to a focused skill such as mcp-builder, component, terminal, ccs, hookify, or agent. It acts as a lightweight decision layer to ensure requests land with the most relevant implementer.

How this skill works

The router evaluates incoming requests against a decision tree of subcategories: MCP development, tooling/CLI, hooks/configuration, and orchestration. It maps trigger keywords to managed skills and forwards the request with context to the selected skill. When ambiguity exists, it prefers the closest semantic match and can fall back to clarifying questions.

When to use it

  • You need to route an MCP server or model-context-protocol task to a specialist skill.
  • You want CLI, automation, or delegation tasks directed to terminal or ccs functionality.
  • You are creating hooks, plugins, or configuration flows and need hookify or component generation.
  • You must orchestrate multi-agent workflows or CI/CD pipelines and require agent or workflow skill support.
  • You want a single entry point for infrastructure/tooling requests to reduce manual routing.

Best practices

  • Include clear trigger words (mcp, server, cli, hook, orchestrate, pipeline) in requests to improve routing accuracy.
  • Provide minimal context fields: desired outcome, environment (dev/prod), and any relevant config files or endpoints.
  • If the task spans categories, state primary goal first so the router picks the most relevant skill.
  • Use follow-up clarifications when the router asks—this reduces misrouted actions and rework.
  • Treat the router as a coordinator; the routed skill performs the concrete implementation steps.

Example use cases

  • Route a request to create an MCP server and receive step-by-step server setup guidance from mcp-builder.
  • Direct a CLI design request to terminal for TUI patterns and UX recommendations.
  • Forward a plugin or hook creation task to hookify to generate hook scaffolding and lifecycle callbacks.
  • Send a multi-agent orchestration requirement to agent to design coordination and state exchange.
  • Delegate a tool spawning or delegation pattern to ccs to produce automation scripts and spawn logic.

FAQ

What triggers decide routing?

Routing relies on explicit trigger keywords in the request like mcp, server, cli, hook, orchestrate, pipeline, deploy, and delegate.

Can the router handle multi-category requests?

Yes. It chooses the primary category based on stated outcome or requests a short clarification when needed.