Plugin Ecosystem

Discover, install, and share agent workflows for the Syntropic137 platform.

Syntropic137 plugins are distributable bundles of workflows for the Syntropic137 platform. Install pre-built plugins from GitHub-hosted marketplaces, or create your own and share them with the community.

# Register a marketplace
syn marketplace add syntropic137/workflow-library

# Search for plugins
syn workflow search "research"

# Install by name
syn workflow install research-toolkit

# Run it
syn workflow run deep-research --task "Analyze our authentication architecture"

Two Plugin Boundaries

Syntropic137 has two distinct plugin concepts. The diagram below shows how they relate:

Syntropic137 Plugins

Bundles of workflows (and eventually triggers) that are ingested into the Syntropic137 platform. These are what you install from marketplaces, export from running workflows, and share with your team. They define what work gets done — the multi-phase execution plans that agents follow inside isolated Docker workspaces.

  • Distributed via GitHub-based marketplaces
  • Manifest: syntropic137-plugin.json
  • Content: workflow.yaml + phase .md files
  • Install: syn workflow install <name>

Claude Code Plugin

A separate project (syntropic137-claude-plugin) that gives Claude Code the context to operate Syntropic137. It provides slash commands (/syn-status, /syn-workflow, etc.) and domain skills that teach Claude Code how to create workflows, kick off executions, query metrics, and manage the platform.

The Claude Code plugin is not a Syntropic137 plugin — it's a Claude Code plugin for using Syntropic137. See Claude Code Integration for details.

Phase Prompt Format

Phase prompts use .md files with optional YAML frontmatter — a convention inspired by Claude Code's custom command format. If you've written Claude Code commands, the format is familiar:

---
model: sonnet
argument-hint: "[topic]"
allowed-tools: Read,Glob,Grep,Bash
max-tokens: 4096
timeout-seconds: 300
---

You are a research assistant investigating: $ARGUMENTS

Use {{discovery}} to reference output from a previous phase.
Frontmatter KeyDescription
modelClaude model (sonnet, opus, haiku)
argument-hintShown to users when prompted for input
allowed-toolsComma-separated list of permitted tools
max-tokensMaximum output tokens for the phase
timeout-secondsPhase execution timeout

Exporting Plugins

Any workflow running in Syntropic137 can be exported as a distributable plugin:

# Export as a package (workflow.yaml + phase .md files)
syn workflow export <workflow-id> --output ./my-plugin/

# Export as a plugin with a Claude Code command wrapper
syn workflow export <workflow-id> --format plugin --output ./my-plugin/

The plugin format adds a commands/syn-*.md wrapper that calls syn workflow run, so the exported workflow can also be invoked as a slash command in Claude Code. The package itself remains a Syntropic137 plugin — the CC command is a convenience bridge.

syntropic137-plugin.json
syn-deep-research.md
workflow.yaml
README.md

Marketplace

The marketplace is a decentralized network of GitHub repositories that serve as plugin registries. Any GitHub repo with a marketplace.json at the root can be a marketplace.

How It Works

  1. Register a marketplace: syn marketplace add org/repo
  2. Search across all registries: syn workflow search "code review"
  3. Install by name: syn workflow install pr-review — the CLI resolves the name from registered marketplaces, clones the repo, and installs the workflows
  4. Update when new versions are available: syn workflow update pr-review
  5. Uninstall when you're done: syn workflow uninstall pr-review

Registry Management

syn marketplace add syntropic137/workflow-library     # Register
syn marketplace add myorg/internal --name my-company  # Custom name
syn marketplace list                                  # List registries
syn marketplace refresh                               # Force cache refresh
syn marketplace remove my-company                     # Remove

Marketplace indexes are cached locally for 4 hours. The CLI refreshes automatically when the cache expires, or you can force it with syn marketplace refresh.

Discovery

# Search by keyword (matches name, description, category, tags)
syn workflow search "research"

# Filter by category or tag
syn workflow search --category research
syn workflow search --tag multi-phase

# Get full details on a specific plugin
syn workflow info research-toolkit

Install, Update, Uninstall

# Install from marketplace by name
syn workflow install research-toolkit

# Check for updates
syn workflow update research-toolkit --dry-run

# Update to latest
syn workflow update research-toolkit

# Uninstall (removes workflows from platform)
syn workflow uninstall research-toolkit

# Uninstall but keep workflows running
syn workflow uninstall research-toolkit --keep-workflows

Updates compare the remote git commit SHA against the installed SHA — if they match, the package is already up to date.

Trigger Support

Trigger bundling in plugins is not yet implemented. Plugins currently contain workflows only. Track progress: #430

The vision is that plugins will include trigger configurations alongside workflows — for example, a "PR Review" plugin that bundles a code review workflow and a trigger that fires it when a pull request is opened. Since triggers need to be attached to specific repos (which vary across setups), the CLI would prompt during install to select target repos.

Triggers exist today as a separate system (syn triggers register/list/pause/resume/delete) but aren't yet part of the plugin package format.

Creating Plugins

Plugins follow a standard package format. See Workflow Packages for the full guide on:

Learn More

Syntropic137 Docs v0.18.0 · Last updated March 2026

On this page