Ops

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 45b1886cf782 · 20 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/opsThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict45b1886cf782A new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: This skill should be used when the user asks to "ops command center", "/ops:ops", or "run the business". Single discovery router for all business operations — communications, projects, infrastructure, revenue,…

---
name: ops
description: "This skill should be used when the user asks to \"ops command center\", \"/ops:ops\", or \"run the business\". Single discovery router for all business operations — communications, projects, infrastructure, revenue, marketing, releases, fleet management, automation, or any OPS capability. Loads and invokes only the relevant specialist instructions on demand."
argument-hint: '[command] [args]'
allowed-tools:
  - Read
  - Skill
effort: medium
maxTurns: 20
---

# OPS — Lazy Capability Router

This is the single broad discovery entry for the OPS plugin. Specialist skill and agent
bodies are intentionally absent from startup context.

## Route

1. If `$ARGUMENTS` is empty, invoke the `ops:ops-dash` skill.
2. Otherwise, read [the capability index](references/capabilities.json).
3. Match the user's complete request—not merely one keyword—to exactly one specialist skill.
4. Invoke that skill through the `Skill` tool using its exact namespaced name:
   `ops:<skill-name>`. Forward the user's original arguments and intent unchanged.
5. If two specialists genuinely fit, choose the narrower one. Ask only when the choice
   would materially change an external action.

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

Do not reproduce or summarize a specialist workflow from the index. Invoke the specialist
so Claude Code loads its full body, allowed tools, effort, hooks, and turn budget on demand.
Never invoke `ops:ops` from this router; that would recurse.

The capability index is routing metadata, not authority to perform an action. All approval,
secrets, outbound-message, destructive-operation, and worktree gates remain owned by the
selected specialist and the global hooks.

Excerpt, first 1,927 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-20
   ✓SAFE B 89 / 100

   first audit · source 45b1886cf782

Questions about Ops

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

Spotted something wrong? Report a correction · Methodology