Orchestrate

What Orchestrate is

Orchestrate is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Orchestrate gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Orchestrate

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/testing/test-orchestrator/commands/orchestrate.md, shared under the repository's MIT license. Read the full file on GitHub.

// test-orchestration.config.js
module.exports = {
  stages: [
    {
      name: 'unit-tests',
      parallel: true,
      tests: ['**/*.unit.test.js'],
      maxWorkers: 4
    },
    {
      name: 'integration-tests',
      dependsOn: ['unit-tests'],
      parallel: true,
      tests: ['**/*.integration.test.js'],
      maxWorkers: 2
    },
    {
      name: 'e2e-tests',
…

# Smart test selection based on changed files
$ test-orchestrator run --changed

Analyzing changes...
  Modified files: 3
  Affected tests: 47 (4% of total)

Executing test plan:
  Stage 1: Unit Tests (32 tests, parallel)
     Completed in 12s
  Stage 2: Integration Tests (12 tests, parallel)
     Completed in 28s
  Stage 3: E2E Tests (3 tests, sequential)
     Completed in 45s

Total: 47 tests in 85s (instead of 18m for full suite)

Before you install

• Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
• Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
• Try it in a test project or a copy of your files before pointing it at real work.
• Pin the version you tested, and review changes before updating.
• Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ