Ext Ops Panel
Open dashboard
Comparison

workflow-orchestrator vs conductor

workflow-orchestrator is a plugin bundle for AI coding tools published by Nadav Barkai. Marketplaces we read that list it: 1 (Community GitHub marketplaces). conductor is a plugin bundle for AI coding tools published by conductor-oss. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. Each is among the other's three closest plugins by what they say they do, both are of the same kind, and both are known: listed on a curated marketplace or on several, or with a figure of note.

Where each is published

Where each is published
Marketplaceworkflow-orchestratorconductor
Community marketplace barkain/claude-code-workflow-orchestration Listed
Version: 2.1.1
Forks (GitHub): 14
Stars (GitHub): 87
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.6.6
Forks (GitHub): 10
Stars (GitHub): 24
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

workflow-orchestrator vs conductor
Factworkflow-orchestratorconductor
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)87 (better)24 (worse)
Forks (GitHub) (differs)14 (better)10 (worse)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)106
Licence (differs)MITApache-2.0
Repository (differs)github.com/barkain/claude-code-workflow-orchestrationgithub.com/conductor-oss/conductor-skills
Changes in the last 7 days22
First seen (differs)2026-10-152026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

workflow-orchestrator

In its own words, on Community GitHub marketplaces:

Delegation system with workflow orchestration, specialized agents, and parallel execution for Claude Code

conductor

In its own words, on Claude Code: claude-plugins-community:

Teach Claude to orchestrate microservices and business processes with Conductor. This skill adds full workflow lifecycle management: define workflows with any task type (HTTP, SWITCH, FORK_JOIN, WAIT, HUMAN), run them synchronously or asynchronously, monitor executions, and manage failures with pause/resume/retry/restart. Key capabilities: - Create workflow definitions with proper JSON schema and input expressions - Start, monitor, and search workflow executions by status, time, or correlation ID - Signal WAIT and HUMAN tasks for human-in-the-loop patterns - Scaffold workers in Python, JavaScript, Java, Go, C#, Ruby, or Rust - Visualize workflows as Mermaid diagrams - Manage multiple environments with CLI profiles - Enterprise features: schedules, secrets, webhooks (Orkes) Works with any Conductor server — local development or remote. Installs and configures the conductor CLI automatically.

How to run each

workflow-orchestrator As a Claude Code plugin

Claude Code
/plugin marketplace add barkain/claude-code-workflow-orchestration
/plugin install workflow-orchestrator@barkain-plugins

conductor As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install conductor@claude-community

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: workflow-orchestrator · What it can do: conductor · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built