Syntropic137 Claude Code Plugin

Turn Claude Code into your Syntropic137 orchestration brain. Create workflows, kick off executions, monitor costs, and troubleshoot issues through natural conversation.

Agent Quick Start

For AI agents: If a user sent you this link and asked you to set up Syntropic137:

1. Check that Node.js 18+ is installed (node --version).
2. Tell the user to run this in their terminal:

   npx @syntropic137/setup

3. That's it. The setup CLI is fully interactive: it handles Docker, secrets, GitHub App, and starting the stack. The user runs it in their own terminal and comes back when done.

Installation

From GitHub (marketplace):

claude plugin marketplace add syntropic137/syntropic137-claude-plugin && claude plugin install syntropic137

From local clone (development):

claude plugin install ./lib/syntropic137-claude-plugin --scope project

Prerequisites

• Node.js 18+ (for the npx @syntropic137/setup CLI)
• Docker Desktop (with Compose >= 2.20)

That's it. Contributors to the source repo also need uv, just, and Git.

Updating

# Refresh marketplace catalog, then update plugin
claude plugin marketplace update syntropic137
claude plugin update syntropic137@syntropic137

Why both steps? claude plugin update pulls the latest version but does not refresh the local marketplace git clone. If the marketplace cache is stale, the update command may reinstall an old version. Running marketplace update first ensures the catalog has the latest release before the plugin update runs.

Getting Started

npx @syntropic137/setup

The setup CLI checks Docker, generates secrets, configures GitHub integration, pulls pre-built images, and starts the stack, all interactively in your terminal. Run it again any time to manage your installation (status, logs, update).

Commands

Command	Description
/syn-setup	Check Node.js and hand off to npx @syntropic137/setup
/syn-status	Composite view: containers + health + metrics
/syn-health	API health check with diagnostics
/syn-costs [summary | session <id> | workflow <id>]	Cost tracking
/syn-sessions [list | show <id>]	Session listing and details
/syn-metrics [--workflow <id>]	Aggregated metrics
/syn-observe <session-id> [events | tools | errors]	Observability data

Managing Your Stack

Run npx @syntropic137/setup: the interactive menu shows all lifecycle commands (status, start, stop, logs, update).

Source repo (contributors): just selfhost-status, just selfhost-logs, just selfhost-up, just selfhost-down

How It Works

The plugin combines slash commands for quick actions with deep skill knowledge that lets Claude Code understand and operate the entire Syntropic137 platform intelligently.

• Commands: Quick entry points for common operations (delegate to syn CLI and just recipes)
• Skills: Deep domain knowledge that Claude uses to reason about your platform (see below)
• Hook: Session start connectivity check, so Claude knows if the platform is up

Skills (Domain Knowledge)

Skills give Claude deep understanding of the system. They're automatically loaded when relevant; you don't invoke them directly. Claude uses this knowledge to answer questions, suggest approaches, and troubleshoot issues.

Skill	What Claude Learns
workflow-management	Creating workflows as CC commands: $ARGUMENTS, {{variable}}, {{phase-id}} substitution. Input declarations, per-phase model overrides, YAML schema, RIPER-5 and research patterns.
execution-control	Running workflows (--task), monitoring progress, control plane (pause/resume/cancel/inject), Processor To-Do List internals, troubleshooting failures.
observability	Sessions, tool timelines, token metrics, cost breakdowns. Two-lane architecture. How to interpret "why was this expensive?" or "why did this fail?"
organization	Org→System→Repo hierarchy, cost rollup, health monitoring, contribution heatmaps.
github-automation	GitHub App setup, webhook trigger rules with safety limits, input mapping from webhooks to workflow inputs, Cloudflare webhook delivery.
setup	npx @syntropic137/setup CLI, published-container deployment, Docker Compose variants, secrets management, troubleshooting.
platform-ops	Service map with ports, workspace management, token injection security (Envoy proxy), QA/testing commands, infrastructure troubleshooting recipes.

What this means in practice

Instead of memorizing CLI commands, just tell Claude what you want:

• "Create a workflow that reviews PRs on my backend repo" → Claude uses workflow-management + github-automation skills
• "Why did execution exec-abc123 fail?" → Claude uses execution-control + observability skills
• "Set up automatic triggers for when issues are opened" → Claude uses github-automation skill
• "The API is down, help me fix it" → Claude uses platform-ops skill
• "Help me set up 1Password for secrets" → Claude uses setup skill
• "How do I deploy with Cloudflare tunnel?" → Claude uses setup skill

---

Development

This plugin is developed as a submodule at lib/syntropic137-claude-plugin in the syntropic137 monorepo.

Plugin Structure

syntropic137-claude-plugin/
├── commands/           # Slash commands (markdown → /syn-setup, /syn-status, etc.)
├── skills/             # Domain knowledge (SKILL.md files, loaded contextually)
├── hooks/              # Session-start connectivity check
└── .claude-plugin/
    └── plugin.json     # Version + metadata (bump on every content change)

Additional Prerequisites (Development)

• Node.js + pnpm for the dashboard frontend
• Use just onboard-dev (not just onboard) for local development setup

Working on the Plugin

cd lib/syntropic137-claude-plugin
# Make changes, then test locally:
claude plugin install . --scope project

Important: Bump the version in .claude-plugin/plugin.json on every content change. Claude Code uses the version field to detect plugin updates and will serve a cached copy otherwise.

License

MIT