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.
npx skills add https://github.com/davepoon/buildwithclaude --skill ops
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.
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter, batch processing lock, session lock expired, idle timeout, connection inactive, link detach, slow reconnect, session error, duplicate events, offset reset, receive batch.
Sub-skill of microsoft-365-agents-toolkit. Routed expert system with 100+ micro-expert files for migrating Slack bots to Teams, cross-platform bridging, and dual-platform bot development. USE FOR: migrating Slack bot to Teams, adding Teams support to Slack bot, building dual-platform bots, converting Block Kit to Adaptive Cards, identity/OAuth bridging, deploying bots to Azure or AWS, configuring AI model providers. DO NOT USE FOR: general web development, non-bot projects, standalone Teams development without Slack (use parent skill instead).
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, service bus queue issue, topic subscription error, enable logging event hub, service bus logging, eventhub python, servicebus java, eventhub javascript, servicebus dotnet, event hub checkpoint, event hub not receiving messages, service bus dead letter, batch processing lock, session lock expired, idle timeout, connection inactive, link detach, slow reconnect, session error, duplicate events, offset reset, receive batch.
Build real-time chat applications with thread management, messaging, participants, and read receipts.
Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
Azure Web PubSub Service SDK for Python. Use for real-time messaging, WebSocket connections, and pub/sub patterns.
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings.
Enterprise messaging with queues, topics, and subscriptions.
Take davepoon/ops from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.