| name | mpm-orchestration-demo |
| description | Reference implementation demonstrating the Command → Agent → Skill orchestration pattern in Claude MPM, showing both preloaded-skill and dynamic-skill-invocation styles |
| argument-hint | [topic] |
| user-invocable | true |
| disable-model-invocation | true |
| version | 1.1.0 |
| category | universal |
| author | Claude MPM Team |
| license | MIT |
| progressive_disclosure | {"entry_point":{"summary":"Canonical MPM orchestration example: Command → Agent → Skill with two invocation styles","when_to_use":"When building new MPM workflows, onboarding to MPM patterns, or referencing orchestration best practices","quick_start":"Run /mpm-orchestration-demo to see the pattern in action"},"references":["orchestration-patterns.md"]} |
| context_limit | 600 |
| tags | ["orchestration","patterns","reference","mpm","agents","skills"] |
| requires_tools | [] |
MPM Orchestration Demo
Overview
This skill is the canonical reference for the Command → Agent → Skill orchestration pattern in Claude MPM. It demonstrates a code review workflow that shows how commands, agents, and skills compose together — and the two distinct ways a skill can be invoked.
Understanding this pattern is the foundation for building any non-trivial MPM workflow.
The Two Invocation Styles
Style 1: Preloaded Skills (Frontmatter)
A skill is listed in an agent's skills: frontmatter. The full skill content is injected into the agent's context at startup, becoming embedded domain knowledge.
---
name: code-reviewer
description: Reviews code for quality, security, and correctness
skills:
- code-review-checklist
model: sonnet
---
When to use: The agent always needs this knowledge. It's core to the agent's purpose — not situational.
Characteristics:
- Content is present from the first turn
- No tool call overhead
- Consumes context tokens even if not needed
- Best for 1–3 essential knowledge bases
Style 2: Dynamic Invocation (Skill Tool)
A skill is invoked at runtime using the Skill tool. The command or agent calls Skill(skill: "skill-name") when it needs that capability.
# In a command or agent's instructions
Skill(skill: "security-scanner")
When to use: The capability is situational — only needed under certain conditions or after gathering initial data.
Characteristics:
- Invoked only when needed
- Preserves context tokens otherwise
- Enables conditional logic ("if security issues found, invoke scanner")
