Ops
Skill ActiveBusiness operations command center. Routes to the right ops command based on what you need — briefing, inbox, fires, projects, comms, triage, linear, revenue, deploy, or yolo mode.
To provide a unified command center for managing diverse business operations tasks through a single interface and intelligent routing.
Features
- Routes commands to specialized operational skills
- Provides a unified business operations dashboard
- Supports agent teams for coordinated operations
- Includes background daemons for pre-warming data
- Integrates with numerous business services
Use Cases
- Get a morning briefing across all business metrics
- Manage projects, revenue, and deployments from one place
- Send and receive messages across multiple communication channels
- Automate operational tasks with specialized agents
Non-Goals
- Directly performing complex operations, instead routing to specialized skills
- Handling tasks outside the defined business operations scope
- Replacing individual service dashboards, but consolidating their key information
Documentation
- warning:Configuration & parameter referenceWhile the SKILL.md outlines routing, it does not explicitly document all configuration parameters or their precedence, relying on external files like preferences.json and daemon-health.json without detailing their schema or defaults.
Code Execution
- info:Error HandlingWhile not explicitly detailed, the routing mechanism and mention of fallback paths suggest a basic level of error handling for routing failures.
Scope
- info:Tool surface sizeThe skill acts as a router to many sub-skills, effectively exposing a large surface area through delegation rather than direct tools.
Errors
- info:Actionable error messagesWhile specific error messages are not detailed, the setup wizard and mention of fallback paths imply that errors would provide some guidance, though explicit remediation steps are not documented.
Practical Utility
- info:Edge casesWhile the routing logic implies handling of empty arguments, specific failure modes and recovery steps for routing errors are not explicitly documented in the SKILL.md.
Safety
- info:Halt on unexpected stateThe skill's routing mechanism implies it would halt if a command doesn't match any defined routes, but explicit preconditions and reporting on unexpected states are not detailed.
Installation
First, add the marketplace
/plugin marketplace add Lifecycle-Innovations-Limited/claude-ops/plugin install claude-ops@ops-marketplaceQuality Score
Trust Signals
Similar Extensions
Acp Router
100Route plain-language requests for Pi, Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either OpenClaw ACP runtime sessions or direct acpx-driven sessions ("telephone game" flow). For coding-agent thread requests, read this skill first, then use only `sessions_spawn` for thread creation. Codex chat binding defaults to the native Codex app-server plugin unless ACP is explicit or background spawn needs ACP.
Ops Go
98Token-efficient morning briefing. Pre-gathers all data via shell scripts, then presents a unified business dashboard with prioritized actions.
Project Session Manager
100Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions
Public Google Drive
100Create public Google Docs or Google Sheet files without requiring OAuth. Use this skill to create and edit Google Docs and Sheets, no Google sign-in required. Documents are viewable at shareable links. Registration is automatic on first use.
Oh My Claudecode
100Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.