Business operations command center. Routes to the right ops command based on what you need — briefing, inbox, fires, projects, comms, triage, linear, revenue, deploy, or yolo mode.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Before routing, load:
cat ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json — read configured channels to determine available commandscat ${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json — if action_needed, surface before routingRoute $ARGUMENTS to the correct ops skill:
| Input | Route to |
|---|---|
| (empty), dash, home, hq | /ops:ops-dash |
| go, morning, briefing | /ops-go |
| setup, configure, init, install | /ops:setup $ARGUMENTS |
| inbox, unread, messages | /ops-inbox |
| comms, send, whatsapp, email, slack, telegram | /ops-comms $ARGUMENTS |
| fires, incidents, down, sentry | /ops-fires |
| projects, dashboard | /ops-projects |
| status, health-status | /ops:ops-status |
| next, priority, what | /ops-next |
| triage, issues | /ops-triage |
| linear, sprint, board | /ops-linear |
| revenue, money, mrr, costs | /ops-revenue |
| deploy, ship | /ops-deploy |
| merge, prs, ship-prs | /ops-merge $ARGUMENTS |
| marketing, email, klaviyo, ads, meta, seo, campaigns | /ops:ops-marketing $ARGUMENTS |
| ecom, shop, shopify, store, orders, inventory | /ops:ops-ecom $ARGUMENTS |
| voice, call, tts, transcribe, phone | /ops:ops-voice $ARGUMENTS |
| yolo | /ops-yolo |
| doctor, health, fix, diagnose | /ops:ops-doctor |
| monitor, apm, alerts, datadog, newrelic, otel | /ops:ops-monitor $ARGUMENTS |
| settings, credentials, creds, config, reconfigure | /ops:ops-settings $ARGUMENTS |
| integrate, connect, add-api, saas, partner | /ops:ops-integrate $ARGUMENTS |
| speedup, clean, optimize, cleanup | /ops:ops-speedup |
| orchestrate, subagents, agents, dispatch, run | /ops:ops-orchestrate $ARGUMENTS |
If $ARGUMENTS is empty, launch the interactive dashboard: invoke /ops:ops-dash directly.
If CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is set, use Agent Teams when building dashboard sections in parallel. This enables:
Team setup (only when flag is enabled):
TeamCreate("ops-team")
Agent(team_name="ops-team", name="daily-ops", prompt="Gather fires, inbox, and unread comms status")
Agent(team_name="ops-team", name="engineering", prompt="Gather PRs, CI status, and deploy state")
Agent(team_name="ops-team", name="business", prompt="Gather revenue, Linear sprint, and project progress")
Agent(team_name="ops-team", name="automation", prompt="Check cron jobs, daemon health, and scheduled tasks")
If the flag is NOT set, use standard fire-and-forget subagents.
This skill is a router only — it does not call CLI tools directly. All tool usage is delegated to the target skill after routing. See the referenced skill's ## CLI/API Reference section for details.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Handle ActiveCampaign contact and marketing tasks through Rube MCP, a connection for agent tools. Find or create contacts, manage tags and subscriptions, enroll contacts in existing automated workflows, and create follow-up tasks.
Research competitors’ live Meta and Google ads to identify opening hooks, offers, calls to action, and landing pages. Receive a sourced creative brief and up to three test ideas adapted to your product.
Analytics your AI agent can actually use. Track, analyze, run A/B experiments, and optimize across all your projects via CLI. Includes a growth playbook so your agent knows HOW to grow, not just what to track.
The English summary is being prepared. Showing the original description.
Teaches when to recall from long-term memory before acting and when to save durable decisions, corrections and failures afterwards. Use when a memory tool or MCP memory server is connected but the agent is not using it consistently, when the user complains that the assistant forgets preferences, conventions or past decisions between sessions, or when setting up persistent memory for a project. Works with any memory backend: a folder of Markdown files, a local MCP server, or a managed service.
The English summary is being prepared. Showing the original description.
Audit local AI coding-agent sessions with agenttrace for cost, tokens, tool failures, latency, anomalies, health, diffs, and CI gates.
The English summary is being prepared. Showing the original description.
Checks which private files (.env, keys, secrets) Claude Code and its subagents reached in this project, whether a value came into an agent's context, and which key to change, by running the open source agentwhy CLI over the session records Claude Code already keeps on disk. Use when the user asks whether the agent or a subagent read their .env or other secrets, which private files a session touched, whether a key leaked into the conversation, or which key to rotate. Runs locally and never prints a secret value.
The English summary is being prepared. Showing the original description.