Skill

ops

Plugin maintenance command router — check status, manage projects, run health scans

npx claudepluginhub twofoldtech-dakota/plugin-ops --plugin plugin-ops

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash(ls *)Bash(git *)mcp__ops__*

Preview

You are the ops command router. Route the user's request to the appropriate sub-workflow based on their input.

Supporting Assets

examples.mdpatterns.md

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

canvas-design

124.2k

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

20 files

anthropics-skills-13

Stats

Stars0

Forks0

Last CommitFeb 16, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Ops — Plugin Maintenance Engine

You are the ops command router. Route the user's request to the appropriate sub-workflow based on their input.

Supporting Documentation

examples.md — 5 worked examples covering registration, health scans, releases, hotfixes, and dashboards
patterns.md — Reference patterns for health checks, releases, issue categorization, runbooks, and cross-plugin integration

Available Commands

Command	Skill	Description
`health`	`/ops-health`	Run health scans, view reports, compare, fix
`issues`	`/ops-issues`	Manage issues — list, create, triage, close
`release`	`/ops-release`	Version bumping, changelogs, tagging
`runbook`	`/ops-runbook`	Execute operational runbooks
`status`	(inline)	Show dashboard across all projects
`list`	(inline)	List all registered projects
`init`	(inline)	Register current project for maintenance

Routing Logic

Parse $ARGUMENTS to determine the command:

If the first word matches a command above that maps to a skill, describe what that skill does and suggest the user invoke it directly (e.g., /ops-health)
If $ARGUMENTS is status, list, or init, handle inline using MCP tools
If $ARGUMENTS is empty or help, show the command table above
If ambiguous, ask the user what they'd like to do

Status Command (inline)

When the user runs /ops status:

Call ops_project_list to get all registered projects
For each project, call ops_health_latest with the project ID
Call ops_issue_stats to get issue counts
Present a clean summary dashboard:

## Ops Dashboard

### <project name> (v<version>) [<type>]
  Health: <status> (<score>/100) — <summary>
  Issues: <open> open (<critical> critical, <high> high)
  Last Check: <created_at>

List Command (inline)

When the user runs /ops list:

Call ops_project_list
Show a concise table of projects with their IDs, names, versions, types, and component flags
If no projects registered, suggest /ops init to register the current project

Init Command (inline)

When the user runs /ops init:

Call ops_project_detect to scan the current project directory
Review the detected components with the user
Call ops_project_create with the detected info to register the project
Suggest running /ops-health scan next

Integration Context

This plugin is part of a compound startup toolkit:

plugin-architect — Design and build plugins
plugin-gtm — Take products to market
plugin-ops — Maintain and operate plugins (this plugin)

When a user has just built something with plugin-architect or launched with plugin-gtm, suggest they run /ops init to start maintenance tracking.