# Ops Dash

OPS on-demand: This skill should be used when the user asks to \"ops dashboard\"...

- Repository: https://github.com/Lifecycle-Innovations-Limited/claude-ops (547 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-dash -g -a claude-code -y`
Codex: `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-dash -g -a codex -y`
Cursor: `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-dash -g -a cursor -y`
Gemini CLI: `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-dash -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Lifecycle-Innovations-Limited/claude-ops`

## Description

OPS on-demand: This skill should be used when the user asks to \"ops dashboard\", \"pixel HQ\", or…

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# OPS > DASH, Interactive Command Center

Load `ops-rules` before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If `AskUserQuestion` / `Workflow` are missing, follow Rule 10 in `ops-rules` (Hermes: numbered options / two-turn Telegram card; `delegate_task`).

## Runtime Context

Before rendering, load available context:

1. **Preferences**: Read `${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json`
   - `owner`, personalize the dashboard header greeting
   - `timezone`, display timestamps correctly in status indicators

2. **Daemon health**: Read `${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json`
   - If `action_needed` is not null → show a warning banner at the top of the dashboard before the menu

## Agent Teams support

If `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` is set, use **Agent Teams** when loading dashboard data in parallel. This enables:

- Agents share context and can coordinate mid-flight
- You can steer priorities in real-time
- Agents report progress as they complete

**Team setup** (only when flag is enabled):

```
TeamCreate("dash-team")
Agent(team_name="dash-team", name="infra-loader", prompt="Gather ECS health, Vercel status, and CI pipeline state")
Agent(team_name="dash-team", name="comms-loader", prompt="Gather unread counts across all configured channels")
Agent(team_name="dash-team", name="projects-loader", prompt="Gather GSD phase, git status, and PRs for all projects")
Agent(team_name="dash-team", name="business-loader", prompt="Gather revenue, Linear sprint, and fire alerts")
```

If the flag is NOT set, use standard fire-and-forget subagents.

## Render dashboard instantly

```!
${CLAUDE_PLUGIN_ROOT}/bin/ops-dash 2>/dev/null || echo "DASH_RENDER_FAILED"
```

## Your task

The dashboard has **already rendered above** via the shell script, the user can see the full colored ANSI output directly. Your job is to **route user input** to the right skill.

The rest: https://github.com/Lifecycle-Innovations-Limited/claude-ops/blob/HEAD/claude-ops/skills/ops-dash/SKILL.md