Agent skill

Ops Status

by Lifecycle-Innovations-Limited in Lifecycle-Innovations-Limited/claude-ops

OPS on-demand: This skill should be used when the user asks to "ops status", "/ops:ops-status", or "are…

MITAuto-check: notes

Install Ops Status

skills CLI

$ npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-status -a claude-code

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

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops 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/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/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/Lifecycle-Innovations-Limited/claude-ops/tree/main/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/Lifecycle-Innovations-Limited/claude-ops/tree/main/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 Lifecycle-Innovations-Limited/claude-ops --skill ops-status -a codex

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

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops 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/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/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/Lifecycle-Innovations-Limited/claude-ops/tree/main/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 Lifecycle-Innovations-Limited/claude-ops --skill ops-status -a cursor

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

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops 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/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/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/Lifecycle-Innovations-Limited/claude-ops/tree/main/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/Lifecycle-Innovations-Limited/claude-ops.git --path 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 Lifecycle-Innovations-Limited/claude-ops --skill ops-status -a gemini-cli

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

GitHub CLI

$ gh skill install Lifecycle-Innovations-Limited/claude-ops 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/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/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/Lifecycle-Innovations-Limited/claude-ops/tree/main/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 Lifecycle-Innovations-Limited/claude-ops 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 Lifecycle-Innovations-Limited/claude-ops --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/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .github/skills && cp -r skills-src/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/Lifecycle-Innovations-Limited/claude-ops/tree/main/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 Lifecycle-Innovations-Limited/claude-ops --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 Lifecycle-Innovations-Limited/claude-ops 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/Lifecycle-Innovations-Limited/claude-ops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/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/Lifecycle-Innovations-Limited/claude-ops/tree/main/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: 542
Token cost: ~1.4k tokens
SKILL.md length: 394 words
Files: 1
Skills in repo: 67
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

OPS on-demand: This skill should be used when the user asks to "ops status", "/ops:ops-status", or "are…

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

What it does

Ops Status is an agent skill from Lifecycle-Innovations-Limited/claude-ops. OPS on-demand: This skill should be used when the user asks to "ops status", "/ops:ops-status", or "are…

Its SKILL.md is about 1.4k 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: Business operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS monitoring, revenue… The licence is MIT.

When your agent uses it

Asks to ops status
/ops:ops-status

Example prompts

“ops status”
“/ops:ops-status”
“/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 ee9c784. 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 1.4k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 394 words of instructions outside code blocks.

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

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 Lifecycle-Innovations-Limited/claude-ops at commit ee9c784, republished under its MIT licence (© Lifecycle-Innovations-Limited). 394 words, ~1,376 tokens.

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

name: ops-status
description: OPS on-demand: This skill should be used when the user asks to "ops status", "/ops:ops-status", or "are…
allowed-tools: Bash, Read, Glob, AskUserQuestion
argument-hint: [--json]
effort: low
maxTurns: 10

OPS ► STATUS

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

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

Show full SKILL.md (122 more words)Show less

Example output

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 OPS ► STATUS — Mon 14 Apr 2026 09:45 UTC
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 CLIs         ✓ gh   ✓ aws  ✓ jq   ✓ node   ✗ whatsapp-bridge
 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", "whatsapp-bridge": "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`

Integration with /ops:setup

/ops:setup (and its --re-setup flag) queries this skill for a per-section health map and uses it to filter the setup selector to only broken/unconfigured sections. The compact shape expected is:

json

{
  "telegram": "green",
  "whatsapp": "missing",
  "email": "red",
  "slack": "green"
}

Maintain this contract when extending the status output — the setup wizard keys on section names like telegram, whatsapp, email, slack, notion, calendar, doppler, vault, ecommerce, marketing, voice, revenue, discord, notifications, github, aws, sentry, linear. A --brief (or equivalent JSON) mode that returns this map is the recommended integration surface.

Files

Just SKILL.md in claude-ops/skills/ops-status of Lifecycle-Innovations-Limited/claude-ops.

Open the folder on GitHubat commit ee9c784

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 skillLifecycle-Innovations-Limited/claude-ops	542	—	~1.4k	Automated safety check: Notes	MIT	today
Knowledge Opsaffaan-m/ECC	276k	2 repos	~1.7k	Automated safety check: Pass	MIT	today
Research Opsaffaan-m/ECC	276k	2 repos	~902	Automated safety check: Pass	MIT	today
Terminal Opsaffaan-m/ECC	276k	2 repos	~750	Automated safety check: Pass	MIT	today
Messages Opsaffaan-m/ECC	276k	1 repos	~724	Automated safety check: Pass	MIT	today
Email Opsaffaan-m/ECC	276k	1 repos	~1.1k	Automated safety check: Pass	MIT	today

Similar skills

Knowledge Ops
affaan-m/ECC
Knowledge base management, ingestion, sync, and retrieval across multiple storage layers (local files, MCP memory, vector stores, Git repos).
276k GitHub starsUsed in 2 repos~1.7k tokens
Knowledge ManagementAuto-check passed
Research Ops
affaan-m/ECC
Evidence-first current-state research workflow for ECC. An agent skill from affaan-m/ECC.
276k GitHub starsUsed in 2 repos~902 tokens
Research & ScienceAuto-check passed
Terminal Ops
affaan-m/ECC
Evidence-first repo execution workflow for ECC. An agent skill from affaan-m/ECC.
276k GitHub starsUsed in 2 repos~750 tokens
Testing & QAAuto-check passed
Messages Ops
affaan-m/ECC
Evidence-first live messaging workflow for ECC. An agent skill from affaan-m/ECC.
276k GitHub starsUsed in 1 repo~724 tokens
Productivity & AutomationAuto-check passed
Email Ops
affaan-m/ECC
Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC.
276k GitHub starsUsed in 1 repo~1.1k tokens
Writing & ContentAuto-check passed
GitHub Ops
affaan-m/ECC
GitHub repository operations, automation, and management. An agent skill from affaan-m/ECC.
276k GitHub starsUsed in 2 repos~1.5k tokens
DevelopmentAuto-check: warnings

Questions about Ops Status

What does Ops Status do?

OPS on-demand: This skill should be used when the user asks to "ops status", "/ops:ops-status", or "are…. Ops Status is an agent skill from Lifecycle-Innovations-Limited/claude-ops.

When should I use Ops Status?

Ops Status fits situations like: asks to ops status; /ops:ops-status.

How do I install Ops Status in Claude Code?

Run `npx skills add Lifecycle-Innovations-Limited/claude-ops --skill ops-status -a claude-code`. Or copy the skill folder (claude-ops/skills/ops-status in Lifecycle-Innovations-Limited/claude-ops) 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 Lifecycle-Innovations-Limited/claude-ops --skill ops-status -a codex`. Or copy the skill folder (claude-ops/skills/ops-status in Lifecycle-Innovations-Limited/claude-ops) 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 Lifecycle-Innovations-Limited/claude-ops --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 1.4k tokens (SKILL.md is roughly 5.5k 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: Knowledge Ops (affaan-m/ECC, 276k stars), Research Ops (affaan-m/ECC, 276k stars), Terminal Ops (affaan-m/ECC, 276k stars) and Messages Ops (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ops Status?

Lifecycle-Innovations-Limited (a GitHub organization) maintains it in Lifecycle-Innovations-Limited/claude-ops, which has 542 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on October 10, 2026.

Source: Lifecycle-Innovations-Limited/claude-ops 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

When your agent uses it

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

Integration with /ops:setup

Files

Compare with similar skills

Similar skills

More from Lifecycle-Innovations-Limited/claude-ops

Questions about Ops Status