dispatcher

name	dispatcher
description	Route tasks to the right skill, orchestrate multi-skill workflows
user-invocable	false

Dispatcher

Master routing table for all skills. Claude reads this to decide which skill(s) to use.

How it works

1. User makes a request
2. Claude loads this dispatcher
3. Matches request to skill(s) in the routing table
4. Loads and executes skill(s) in order
5. Runs post-execution checklist

Step 1: Read the request

Understand what the user wants. Look for keywords, intent, and context.

Step 2: Skill Routing Table

Match the request to the appropriate skill(s):

Development

Trigger	Skill	What it does
"review this PR", "code review", "check my code"	code-review	Structured code review with checklist
"create branch", "merge PR", "git workflow"	git-workflow	Branch → PR → squash merge → cleanup

Daily Operations

Trigger	Skill	What it does
"what should I do today", "morning summary"	daily-summary	Tasks, PRs, priorities for today
"remember this", "project context", "what do we know about X"	project-notes	Persistent project knowledge base

Add Your Skills Here

Step 3: Multi-Skill Orchestration

Some tasks require multiple skills in sequence. Examples:

Code Review + Deploy

User: "Review and deploy the PR"
1. code-review → check code quality
2. git-workflow → merge PR
3. [your deploy skill] → deploy to environment

Morning Routine

User: "Good morning"
1. daily-summary → show priorities
2. [your inbox skill] → check unread messages
3. [your calendar skill] → show today's meetings

Adding Orchestration Patterns

When you add new skills, think about how they compose:

• What skills naturally chain together?
• What's the correct order?
• What data flows between skills?

Document common chains here so Claude can execute them automatically.

Step 4: Post-Execution Checklist

After executing any skill:

• Did the skill complete successfully?
• Were there any errors to report?
• Should any follow-up tasks be created?
• Does the user need to take any manual action?
• Should this be logged or tracked?

New Skill Registration Checklist

When adding a new skill to the system:

1. Create SKILL.md with frontmatter (name, description)

   cp skills/TEMPLATE.md skills/{category}/{skill-name}/SKILL.md
   

2. Add symlink

   ln -s $(pwd)/skills/{category}/{skill-name} ~/.claude/skills/{skill-name}
   

   Or just run bash setup/install.sh

3. Update this dispatcher — add the skill to the routing table above (this step is critical and easy to forget!)

4. Verify discovery

   ls -la ~/.claude/skills/{skill-name}
   

5. Commit

   git add -A && git commit -m "Add {skill-name} skill"