Summary
Extend conductor templates to support a remote registry for discovering and sharing community workflows — like Homebrew formulae but for conductor workflows.
Motivation
Reusable workflow components are becoming expected across the AI agent ecosystem (MCP server registries, Codex plugin marketplace, Klaw.sh skills marketplace). Conductor has built-in templates today (simple.yaml, loop.yaml, human-gate.yaml) but no way to share or discover community workflows.
Proposed Design
CLI Commands
conductor templates --remote # list community workflows
conductor init my-project --template registry:research-pipeline # scaffold from registry
conductor publish my-workflow.yaml # share to registry (with validation)
Registry Backend
- Simple GitHub repo with YAML files (similar to Homebrew formulae)
- Validation gate on publish to prevent malicious workflows
- Metadata: name, description, author, tags, conductor version compatibility
Why It Fits Conductor
- Builds on existing template infrastructure
- No new runtime concepts — just a distribution mechanism
- YAML-native, version-controllable
- Community safety: validation prevents malicious workflows (15% of OpenClaw community skills were found to contain malicious instructions — validation is essential)
Effort Estimate
Low — extends existing template CLI commands with a remote source.
Summary
Extend
conductor templatesto support a remote registry for discovering and sharing community workflows — like Homebrew formulae but for conductor workflows.Motivation
Reusable workflow components are becoming expected across the AI agent ecosystem (MCP server registries, Codex plugin marketplace, Klaw.sh skills marketplace). Conductor has built-in templates today (
simple.yaml,loop.yaml,human-gate.yaml) but no way to share or discover community workflows.Proposed Design
CLI Commands
Registry Backend
Why It Fits Conductor
Effort Estimate
Low — extends existing template CLI commands with a remote source.