菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Interactive OAuth init wizard for the multi-account Claude rotator. Walks through every account in the rotation config and, for any account missing a valid keychain token, delegates to the proven `rotate.mjs` magic-link flow (browser-driver cascade + Gmail polling), which writes the verified OAuth token to `Claude-Rotation-<key>` (key = account label or email, keychain account `$USER`). Re-runnable any time. Standalone alias of the same step inside `/ops:setup`.
Multi-account Claude Max rotator. Status, manual rotation, account list, add-account wizard, and CRS relay-pool auto-prioritization. Requires account_rotation_enabled=true in plugin settings.
Full inbox management across all channels — WhatsApp (whatsmeow bridge via mcp__whatsapp__*), iMessage (chat.db reader + AppleScript send via mcp__plugin_imessage_imessage__*), Email (Gmail MCP), Slack (MCP), Telegram (user-auth MCP), Discord (webhook + REST read), Notion (MCP — comments, mentions, assigned tasks). Scans FULL inbox (not just unread), identifies messages needing replies, archives handled conversations.
Read-only AWS account hygiene audit — security baseline, unused/orphaned resources, and cost optimization across all configured regions. Produces severity-ranked findings (CRITICAL→LOW) plus a machine-readable findings.json. Cleanup actions are always human-gated, never automatic. Use for cost reviews, security sweeps, recurring account hygiene, or "audit my AWS".
Token-efficient morning briefing. Pre-gathers all data via shell scripts, then presents a unified business dashboard with prioritized actions.
Revenue and costs tracker. AWS spend via aws ce, credits tracker, project revenue stages. Shows burn rate, runway estimate, credits expiring.
| name | ops |
| description | 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. |
| argument-hint | [command] [args] |
| allowed-tools | ["Bash","Read","Grep","Glob","Skill","Agent","TeamCreate","SendMessage"] |
| effort | medium |
| maxTurns | 20 |
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, 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 |
| feature, feature-dev, fd, architect-feature, explore-feature | /ops:ops-feature-dev $ARGUMENTS |
| secret-sync, secrets, doppler-sync, drift | /ops:ops-secret-sync $ARGUMENTS |
| home, homey, lights, flow, scene, energy, climate, presence, alarm, smart-home, iot, thermostat, dim, door, lock | /ops:ops-home $ARGUMENTS |
| statusline, status-line, cockpit | /ops:statusline $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.