Agent skill

Ops Status

Lightweight green/red status panel for every configured integration.

MITAuto-check: notes

Install Ops Status

skills CLI

$ npx skills add davepoon/buildwithclaude --skill ops-status -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install davepoon/buildwithclaude ops-status --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/claude-ops/skills/ops-status .claude/skills/ops-status && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "ops-status" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/claude-ops/skills/ops-status into .claude/skills/ops-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-status", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/davepoon/buildwithclaude/tree/main/plugins/claude-ops/skills/ops-status

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add davepoon/buildwithclaude --skill ops-status -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install davepoon/buildwithclaude ops-status --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/claude-ops/skills/ops-status .agents/skills/ops-status && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ops-status" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/claude-ops/skills/ops-status into .agents/skills/ops-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-status", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add davepoon/buildwithclaude --skill ops-status -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install davepoon/buildwithclaude ops-status --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/claude-ops/skills/ops-status .cursor/skills/ops-status && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ops-status" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/claude-ops/skills/ops-status into .cursor/skills/ops-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-status", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/davepoon/buildwithclaude.git --path plugins/claude-ops/skills/ops-status

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add davepoon/buildwithclaude --skill ops-status -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install davepoon/buildwithclaude ops-status --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/claude-ops/skills/ops-status .gemini/skills/ops-status && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ops-status" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/claude-ops/skills/ops-status into .gemini/skills/ops-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-status", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install davepoon/buildwithclaude ops-status

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add davepoon/buildwithclaude --skill ops-status -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/claude-ops/skills/ops-status .github/skills/ops-status && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ops-status" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/claude-ops/skills/ops-status into .github/skills/ops-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-status", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add davepoon/buildwithclaude --skill ops-status -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install davepoon/buildwithclaude ops-status --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/claude-ops/skills/ops-status .opencode/skills/ops-status && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ops-status" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/claude-ops/skills/ops-status into .opencode/skills/ops-status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ops-status", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ops-status
GitHub stars: 3.6k
Token cost: ~953 tokens
SKILL.md length: 279 words
Files: 1
Skills in repo: 245
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Lightweight green/red status panel for every configured integration.

Works in 2 steps: Preferences: cat… → Daemon health: cat…
SKILL.md covers Runtime Context, CLI/API Reference, What this skill does and Example output, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ops Status is an agent skill from davepoon/buildwithclaude. Lightweight green/red status panel for every configured integration. No gather, no actions.

Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A single hub to find Claude Skills, Agents, Commands, Hooks, Plugins, and Marketplace collections to extend Claude Code, Claude Desktop, Agent SDK and OpenClaw. The licence is MIT.

Example prompts

“/ops-status”

Requirements

Pre-approved tools (allowed-tools): Bash, Read, Glob, AskUserQuestion

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

Preferences: cat ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json — determines which…
Daemon health: cat ${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json — tells the panel whether the daemon row should show ✓ running or ○ not…

What it can do on your machine

Read from SKILL.md and the folder at commit 10bfc43. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash
- Read
- Glob
- AskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ops Status loads about 953 tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 279 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~26
When it runs · the whole SKILL.md, loaded when a task matches: ~953

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Bash, Read, Glob, AskUserQuestion
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davepoon/buildwithclaude at commit 10bfc43, republished under its MIT licence (© davepoon). 279 words, ~953 tokens.

Download SKILL.mdSave it as .claude/skills/ops-status/SKILL.md (or your agent's skills folder).

name: ops-status
description: Lightweight green/red status panel for every configured integration. No gather, no actions.
allowed-tools: Bash, Read, Glob, AskUserQuestion
argument-hint: [--json]
effort: low
maxTurns: 10

OPS ► STATUS

Compact health panel for every configured integration. Much lighter than /ops:go — no gathering, no actions, no heavy API probes. Each row is tagged with ✓ (ok) / ○ (not configured) / ✗ (missing) / ─ (category unused).

Runtime Context

Before rendering, load:

Preferences: cat ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json — determines which integrations are configured
Daemon health: cat ${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json — tells the panel whether the daemon row should show ✓ running or ○ not running

Both are consumed by the bin/ops-status script internally — this skill does not parse them itself.

CLI/API Reference

bin/ops-status

Command	Usage	Output
`${CLAUDE_PLUGIN_ROOT}/bin/ops-status`	Render the pretty text panel	ASCII panel with one row per category
`${CLAUDE_PLUGIN_ROOT}/bin/ops-status --json`	Machine-readable output	Flat JSON: `{clis, channels, mcps, commerce, voice, monitoring, daemon, registry, generated_at}`

Each integration resolves to one of four status strings:

Status	Meaning	Rendered as
`ok`	Installed / credentialed / running	`✓`
`not-configured`	Known slot, no credential recorded	`○`
`missing`	Required but not resolvable	`✗`
`skipped`	User explicitly opted out via `/ops:setup`	`○`

The script is designed to run in under 1 second with no network calls.

What this skill does

Run the status script and print its output verbatim:

${CLAUDE_PLUGIN_ROOT}/bin/ops-status $ARGUMENTS

If $ARGUMENTS contains --json, pass it through — the script emits machine-readable JSON instead of the pretty panel.
Do NOT probe any integration beyond what the script already did. Do NOT spawn a doctor / fix agent. Do NOT run API calls. If the user wants deeper checks, point them at:
- /ops:doctor — full health check + auto-repair
- /ops:go — full morning briefing with live data

Example output

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 OPS ► STATUS — Mon 14 Apr 2026 09:45 UTC
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 CLIs         ✓ gh   ✓ aws  ✓ jq   ✓ node   ✗ wacli
 Channels     ✓ gog   ✓ slack  ○ telegram   ✗ whatsapp
 MCPs         ✓ linear  ✓ sentry  ✓ vercel  ○ gmail
 Commerce     ○ shopify
 Voice        ─ (not configured)
 Monitoring   ✓ datadog  ○ newrelic
 Daemon       ✓ running (6 services, last-sync 2m ago)
 Registry     ✓ 3 projects
──────────────────────────────────────────────────────

JSON shape

json

{
  "clis": {"gh": "ok", "aws": "ok", "jq": "ok", "node": "ok", "wacli": "missing"},
  "channels": {"whatsapp": "ok", "slack": "ok", "telegram": "not-configured"},
  "mcps": {"linear": "ok", "sentry": "ok", "vercel": "ok", "gmail": "not-configured"},
  "commerce": {"shopify": "not-configured"},
  "voice": {},
  "monitoring": {"datadog": "ok", "newrelic": "not-configured"},
  "daemon": {"state": "ok", "services": 6, "last_sync": "2026-04-14T09:43:00Z"},
  "registry": {"state": "ok", "projects": 3},
  "generated_at": "2026-04-14T09:45:12Z"
}

When to use this vs other skills

If you want...	Use
A quick "is everything connected?" glance	`/ops:status`
The full morning briefing with real data	`/ops:go`
Deep diagnostics + auto-repair	`/ops:doctor`
An interactive dashboard with hotkeys	`/ops:dash`

Files

Just SKILL.md in plugins/claude-ops/skills/ops-status of davepoon/buildwithclaude.

Open the folder on GitHubat commit 10bfc43

Compare with similar skills

Ops Status next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ops Status compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ops Status this skilldavepoon/buildwithclaude	3.6k	—	~953	Automated safety check: Notes	MIT	yesterday
Red Green FixComfy-Org/ComfyUI_frontend	2.1k	—	~1.9k	Automated safety check: Pass	GPL-3.0	today
Red Green Refactorrohitg00/skillkit	1.5k	—	~1.3k	Automated safety check: Pass	Apache-2.0	4 mo ago
Configure Channelopenclaw/openclaw	392k	—	~946	Automated safety check: Pass	MIT	today
TDD Red Green Refactorgoogle-labs-code/stitch-sdk	1.8k	—	~755	Automated safety check: Pass	Apache-2.0	7 days ago
ConfigurationBuilderIO/agent-native	7.1k	—	~2.1k	Automated safety check: Pass	None	today

Similar skills

Red Green Fix
Comfy-Org/ComfyUI_frontend
Bug fix workflow that proves test validity with a red-then-green CI sequence.
2.1k GitHub stars~1.9k tokensUpdated today
Testing & QAAuto-check passed
Red Green Refactor
rohitg00/skillkit
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green.
1.5k GitHub stars~1.3k tokensUpdated 4 mo ago
Testing & QAAuto-check passed
Configure Channel
openclaw/openclaw
Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs.
392k GitHub stars~946 tokensUpdated today
Auto-check passed
TDD Red Green Refactor
google-labs-code/stitch-sdk
Official
Enforces a disciplined Red-Green-Refactor (TDD) workflow in TypeScript/Node.js.
1.8k GitHub stars~755 tokensUpdated 7 days ago
Testing & QAAuto-check passed
Configuration
BuilderIO/agent-native
Where a configuration value belongs — app config schema, agent-native.config.ts, or an environment variable — and how the layers resolve.
7.1k GitHub stars~2.1k tokensUpdated today
DevOps & CloudAuto-check passed
Blue Green Deploy
sickn33/agentic-awesome-skills
Configure zero-downtime deployment strategies including blue-green, canary, and rolling deployments.
47k GitHub starsUsed in 1 repo~2.6k tokens
DevOps & CloudAuto-check passed

Questions about Ops Status

What does Ops Status do?

Lightweight green/red status panel for every configured integration. Ops Status is an agent skill from davepoon/buildwithclaude. Lightweight green/red status panel for every configured integration.

How do I install Ops Status in Claude Code?

Run `npx skills add davepoon/buildwithclaude --skill ops-status -a claude-code`. Or copy the skill folder (plugins/claude-ops/skills/ops-status in davepoon/buildwithclaude) into .claude/skills/ops-status in your project. Claude Code loads it when a task matches its description.

How do I install Ops Status in Codex?

Run `npx skills add davepoon/buildwithclaude --skill ops-status -a codex`. Or copy the skill folder (plugins/claude-ops/skills/ops-status in davepoon/buildwithclaude) into .agents/skills/ops-status in your project. Codex loads it when a task matches its description.

Can I use Ops Status in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davepoon/buildwithclaude --skill ops-status -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ops-status, .gemini/skills/ops-status, .github/skills/ops-status and .opencode/skills/ops-status in your project.

What does Ops Status need to run?

SKILL.md names no scripts, command-line tools or credentials: Ops Status is instructions for the agent only. Its frontmatter pre-approves these tools: Bash, Read, Glob, AskUserQuestion.

Does Ops Status access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ops Status safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Ops Status use?

Ops Status is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ops Status use?

About 953 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ops Status?

Skills that share tags, products or a category with Ops Status: Red Green Fix (Comfy-Org/ComfyUI_frontend, 2.1k stars), Red Green Refactor (rohitg00/skillkit, 1.5k stars), Configure Channel (openclaw/openclaw, 392k stars) and TDD Red Green Refactor (google-labs-code/stitch-sdk, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ops Status?

davepoon (a GitHub user) maintains it in davepoon/buildwithclaude, which has 3,604 GitHub stars. The repository holds 245 skills in this directory. The repository was last updated on October 6, 2026.

Source: davepoon/buildwithclaude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Ops Status

Facts

At a glance

What it does

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

OPS ► STATUS

Runtime Context

CLI/API Reference

bin/ops-status

What this skill does

Example output

JSON shape

When to use this vs other skills

Files

Compare with similar skills

Similar skills

More from davepoon/buildwithclaude

Questions about Ops Status