opslisted

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.
Lifecycle-Innovations-Limited/claude-ops · ★ 17 · AI & Automation · score 86

Install: claude install-skill Lifecycle-Innovations-Limited/claude-ops

## Runtime Context Before routing, load: 1. **Preferences**: `cat ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json` — read configured channels to determine available commands 2. **Daemon health**: `cat ${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json` — if `action_needed`, surface before routing # OPS — Business Command Center Route `$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