orchestrator

/orchestrator

Verified AI-agent workflow orchestrator for Claude Code. Dispatch workers, run independent checks, ship only what passes.

Claude Code:

/plugin marketplace add maxtechera/orchestrator

OpenClaw:

clawhub install orchestrator

Zero config. Run /orchestrator sweep immediately — if no board is connected, the setup wizard runs automatically.

---

Install

Claude Code

Install

/plugin marketplace add maxtechera/orchestrator

Update

claude plugin update orchestrator@orchestrator

OpenClaw

clawhub install orchestrator

Manual

git clone https://github.com/maxtechera/orchestrator.git ~/.claude/skills/orchestrator

The agent that did the work never grades its own homework. A separate verification pass runs with fresh context — real API calls, screenshots, link checks, compliance validation. Not another AI saying "looks good."

The core pattern: Ticket contract (Inputs / Deliverables / Verification / Artifacts) → dispatch worker agent → independent verifier → evidence posted to ticket. One cycle, every ticket.

Best for: operators running agentic teams who want verified output, not just agent output.

That's it. Run /orchestrator sweep to get started. If no board is connected, the orchestrator will prompt you to run /orchestrator setup. See Your First Ticket below for a copy-paste template.

Learn /orchestrator

Want the full operating system behind reliable agent teams?

• Course: /orchestrator course outline
• Free lesson workbook: The context-limit wall and why single-agent workflows break
• Paid course CTA: Aprendé a orquestar equipos de agentes → curso /orchestrator ($197)

The free OSS skill helps you run the workflow. The paid course teaches you how to design the contracts, memory, reliability layers, and production patterns behind it.

Marketplace packaging playbooks

If you are preparing a companion skill or repo for Claude Code marketplace submission, use these proof-first packaging docs:

• Memory marketplace optimization package
• MAX-534 proof pack

The memory package includes the final GitHub description, topic set, social preview card, manifest verification checklist, and install steps to copy into the target repo README before submitting.

---

What people use it for

Running a content operation. /orchestrator sweep reads all open tickets, dispatches content agents loaded with your brand voice, and independently verifies every deliverable before marking it done. Not just "here's a draft" — checked output.

Managing an e-commerce store. Set BOARD_PROVIDER=linear and connect Shopify. The orchestrator processes inventory updates, price changes, and product listings — and verifies prices, compare-at fields, and image counts before closing tickets.

Engineering ticket flow. /orchestrator sweep picks up GitHub Issues, runs domain-specific verification (link checks, schema validation, test presence), and only marks tickets done when the deliverable actually passes.

Auditing before a release. /orchestrator review <ticket> independently checks a specific deliverable. The agent that did the work never grades its own homework.

---

Setup: Progressive Integration Unlocking

Start using /orchestrator immediately. Add integrations when you want more domains.

1. Zero Config (built-in skills) — Just install

Run /orchestrator sweep. The orchestrator uses your existing board connections (MCP servers for Linear, GitHub, etc.) and built-in agent capabilities. No API keys, no configuration. If no board is detected, you'll be prompted to run /orchestrator setup.

2. Run the setup wizard (connect your board)

/orchestrator setup

The setup wizard detects your environment, connects your issue tracker, and validates integrations. Takes about 30 seconds. Supports Linear, GitHub Issues, Notion, and Jira. It writes BOARD_PROVIDER and your API key to ~/.config/orchestrator/.env.

If you prefer manual config:

mkdir -p ~/.config/orchestrator && chmod 700 ~/.config/orchestrator

Then add to ~/.config/orchestrator/.env:

# Add to ~/.config/orchestrator/.env
BOARD_PROVIDER=linear        # or: github, notion, jira
LINEAR_API_KEY=lin_api_xxxxx  # swap for your tracker's key

3. Add domain skills (RECOMMENDED — the single most impactful upgrade)

Domain skills give agents real expertise — domain-specific rules, verification criteria, and best practices learned from actual executions. Without them, agents use general capabilities. With them, they follow rules like "carousel images must be 1080x1350" and "always verify compare-at price is cleared when not on sale."

Domain skills are composition wrappers — they load maxtechera/ship and maxtechera/memory skills and add domain-specific verification rules on top. Install ship and memory first, then the domain skill activates their capabilities for orchestrator verification. See skills/README.md for the full list and their composition chains.

/plugin marketplace add maxtechera/skill-content
/plugin marketplace add maxtechera/skill-ecommerce
/plugin marketplace add maxtechera/skill-seo

4. Add Shopify (e-commerce verification)

Connect your Shopify store for automated price, inventory, and product verification.

# Add to ~/.config/orchestrator/.env
SHOPIFY_ACCESS_TOKEN=shpat_xxxxx

5. Add MailerLite (content/newsletter verification)

Free tier at mailerlite.com. Enables email sequence verification — link checks, segment validation, send tests.

# Add to ~/.config/orchestrator/.env
MAILERLITE_API_KEY=xxxxx

6. Add Apollo (sales verification)

Free tier at apollo.io. Enables lead sourcing verification — bounce rate, compliance, sequence validation.

# Add to ~/.config/orchestrator/.env
APOLLO_API_KEY=xxxxx

7. Optional integrations

# Add to ~/.config/orchestrator/.env
META_ADS_TOKEN=xxxxx          # Meta Ads — campaign management
GOOGLE_ADS_TOKEN=xxxxx        # Google Ads — campaign management
GA4_PROPERTY_ID=xxxxx         # Google Analytics — conversions
HUBSPOT_API_KEY=xxxxx         # HubSpot — CRM, pipeline
STRIPE_SECRET_KEY=xxxxx       # Stripe — payment verification
QUICKBOOKS_TOKEN=xxxxx        # QuickBooks — invoicing, AR
XERO_TOKEN=xxxxx              # Xero — alternative to QuickBooks
ZENDESK_TOKEN=xxxxx           # Zendesk — support ticket management
MERCADOLIBRE_TOKEN=xxxxx      # MercadoLibre — LATAM marketplace
INSTAGRAM_ACCESS_TOKEN=xxxxx  # Instagram Graph API — post publishing

The orchestrator validates every connection before dispatching. Missing integrations fail early with a clear message — not midway through execution.

---

Do I need API keys?