Claude Code Orchestrator

A skill-based orchestration framework for Claude Code. Turn your Claude Code into a structured, repeatable system with domain-specific skills, routing, and persistent knowledge.

The Problem

Claude Code is powerful out of the box, but every session starts from scratch. You explain your project structure, conventions, and workflows again and again. Complex tasks require you to manually coordinate multiple steps.

The Solution

Skills — modular instruction sets that teach Claude Code your domain. Each skill is a markdown file that tells Claude exactly how to handle a specific task: what files to read, what commands to run, what to check, and what to avoid.

Dispatcher — a routing table that automatically selects the right skill(s) for any request and orchestrates multi-skill workflows.

You: "Review the PR and deploy to staging"

Dispatcher → code-review skill → deploy skill → notification skill

How It Works

~/.claude/skills/              ← Claude Code auto-discovers skills here
    ├── git-workflow/          ← Symlink → your-repo/skills/.../git-workflow/
    ├── code-review/           ← Symlink → your-repo/skills/.../code-review/
    ├── deploy/                ← Symlink → your-repo/skills/.../deploy/
    └── dispatcher/            ← The brain — routes tasks to skills

your-repo/skills/              ← Organized by category
    ├── core/
    │   └── dispatcher/SKILL.md
    ├── dev/
    │   ├── git-workflow/SKILL.md
    │   └── code-review/SKILL.md
    ├── ops/
    │   └── deploy/SKILL.md
    └── TEMPLATE.md

1. Skills live in a git repo, organized by category
2. Symlinks in ~/.claude/skills/ point to the repo (Claude Code auto-discovers them)
3. Dispatcher routes requests to the right skill(s)
4. Config maps path variables so skills work on any machine

Quick Start

# 1. Clone
git clone https://github.com/anthroos/claude-code-orchestrator.git
cd claude-code-orchestrator

# 2. Configure paths
cp setup/config.example.yaml setup/config.yaml
# Edit config.yaml with your project paths

# 3. Install symlinks
bash setup/install.sh

# 4. Verify
ls -la ~/.claude/skills/
# You should see symlinks to your skills

# 5. Use Claude Code as usual — skills are auto-discovered
claude

Example Skills Included

Skill	Description
dispatcher	Routes tasks to skills, orchestrates multi-skill workflows
git-workflow	Branch → PR → squash merge → delete branch
code-review	Structured code review with checklist
daily-summary	Morning summary of tasks, PRs, and priorities
project-notes	Persistent project knowledge base

These are starting points. The real power comes from writing skills for your domain.

Creating Your Own Skill

# 1. Copy the template
cp skills/TEMPLATE.md skills/your-category/your-skill/SKILL.md

# 2. Edit the skill
# Add frontmatter, triggers, steps, examples

# 3. Update dispatcher routing table
# Add your skill to skills/core/dispatcher/SKILL.md

# 4. Install
bash setup/install.sh

# 5. Commit
git add -A && git commit -m "Add your-skill"

Skill Format

Every skill is a SKILL.md file with YAML frontmatter:

---
name: my-skill
description: What this skill does (shown in Claude Code's skill list)
---

# My Skill

> One-line description

## When to use
- "Deploy the app"
- "Push to production"

## How to execute

### Step 1: Pre-checks
\```bash
git status
\```

### Step 2: Deploy
\```bash
./deploy.sh
\```

## Troubleshooting
| Problem | Solution |
|---------|----------|
| Build fails | Check Node version |

See Skill Guide for the full format reference.

Architecture

Why Symlinks?

Claude Code discovers skills from a flat ~/.claude/skills/ directory. But organizing 50+ skills by category is crucial for maintenance. Symlinks bridge the gap:

• Git repo: organized by category (skills/dev/, skills/ops/, skills/crm/)
• ~/.claude/skills/: flat, auto-discovered by Claude Code
• install.sh: creates the symlinks automatically

Multi-Skill Orchestration

The dispatcher enables chaining:

User: "Prepare for the client call tomorrow"

Dispatcher routes to:
1. calendar-check → find meeting details
2. project-notes → load client context
3. task-list → find pending items
4. call-prep → generate agenda

Each skill has clear inputs/outputs and can be composed with others.

Configuration

Skills use path variables ($PROJECT_ROOT, $DOCS_PATH) instead of hardcoded paths. Define them once in setup/config.yaml:

paths:
  project_root: ~/my-project
  docs: ~/my-project/docs
  scripts: ~/my-project/scripts

Scaling

This system has been battle-tested with 60+ skills across CRM, project management, sales, finance, DevOps, and communication channels. It scales well because:

• Skills are modular — add/remove without affecting others
• Skills are discoverable — Claude Code finds them automatically
• Skills are composable — the dispatcher chains them
• Skills are versionable — they live in git

Requirements

• Claude Code CLI
• Bash (for install script)
• Git

License

MIT

Credits

Built by WeLabelData. Extracted from a production system running 60+ skills daily.