Ops Dash

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 90a91797a66f · 26 Oct 2026Report an issue or request a re-scan

• PublisherLifecycle-Innovations-Limited GitHub organizationOwner of the repository this skill is read from
• Source folderLifecycle-Innovations-Limited/claude-ops/claude-ops/skills/ops-dashThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict90a91797a66fA new audit runs when the source changes
• Repository statusNot archivedLast push 2 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

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

---
name: ops-dash
description: "OPS on-demand: This skill should be used when the user asks to \"ops dashboard\", \"pixel HQ\", or..."
argument-hint: '[back|settings|share|faq]'
allowed-tools:
  - Bash
  - Read
  - Grep
  - Glob
  - Skill
  - Agent
  - TeamCreate
  - SendMessage
  - AskUserQuestion
  - CronCreate
  - CronList
  - CronDelete
effort: low
maxTurns: 15
disallowedTools:
  - Edit
  - Write
  - NotebookEdit
---

# 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.

**DO NOT re-render, re-print, summarize, transcribe, or describe the dashboard output.** The user sees the rich colored render above; any plain-text re-statement is duplicate noise and destroys the visual quality.

Skip straight to AskUserQuestion for the next action — no preamble, no recap, no "vitals" summary line. The dashboard speaks for itself.

## Routing table

| Input                               | Route                   | Description                                                                |
| ----------------------------------- | ----------------------- | -------------------------------------------------------------------------- |
| `1`, `go`, `morning`, `briefing`    | `/ops:ops-go`           | Morning briefing                                                           |
| `2`, `inbox`, `unread`, `messages`  | `/ops:ops-inbox`        | Inbox zero                                                                 |
| `3`, `fires`, `incidents`, `down`   | `/ops:ops-fires`        | Fire check                                                                 |
| `4`, `projects`, `portfolio`        | `/ops:ops-projects`     | Project dashboard                                                          |
| `5`, `next`, `priority`, `what`     | `/ops:ops-next`         | What's next                                                                |
| `6`, `revenue`, `costs`, `money`    | `/ops:ops-revenue`      | Revenue & costs                                                            |
| `7`, `linear`, `sprint`, `board`    | `/ops:ops-linear`       | Linear sprint                                                              |
| `8`, `deploy`, `ship`               | `/ops:ops-deploy`       | Deploy status                                                              |
| `9`, `triage`, `issues`             | `/ops:ops-triage`       | Triage issues                                                              |
| `0`, `speedup`, `clean`, `optimize` | `/ops:ops-speedup`      | System speedup                                                             |
| `a`, `yolo`                         | `/ops:ops-yolo`         | YOLO mode                                                                  |
| `b`, `merge`, `prs`                 | `/ops:ops-merge`        | Auto-merge PRs                                                             |
| `c`, `setup`, `configure`           | `/ops:setup`            | Setup wizard                                                               |
| `d`, `send`, `comms`                | `/ops:ops-comms`        | Send message                                                               |
| `e`, `report`, `csuite`             | Read latest YOLO report | C-suite report                                                             |
| `f`, `settings`, `prefs`, `config`  | Settings sub-menu       | Interactive config                                                         |
| `g`, `share`                        | Share sub-menu          | Share your setup                                                           |
| `h`, `home`, `homey`, `house`       | `/ops:ops-home`         | Smart-home control (only if `home_automation` configured in `$PREFS_PATH`) |
| `?`, `faq`, `help`, `wiki`          | FAQ sub-menu            | Help & FAQ                                                                 |
| `back`, `dash`                      | Re-render dashboard     | Return to dash                                                             |

---

## C-suite report access (option e)

When user selects `e`:

1.

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

1. 2026-10-26
   ✓SAFE B 89 / 100

   first audit · source 90a91797a66f

Questions about Ops Dash

• github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/cl — the audited source at commit 90a91797a66f and every finding aboveObserved · 26 Oct 2026

Spotted something wrong? Report a correction · Methodology