ops-mcp

Featured

OPS on-demand: This skill should be used when the user asks to "MCP down", "reconnect MCP", or…

AI & Automation 188 stars 22 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
76
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# OPS ► MCP 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`). Surfaces the MCP auto-reconnect subsystem (watchdog + keepalive + reauth) as a discoverable slash command. These three scripts were previously orphaned — no plugin-level entry point. This skill is the entry point. For full architecture reference (state files, scripts, failure modes) see [`STATUS.md`](./STATUS.md). ## Runtime Context Before any route runs, resolve: 1. **State dir**: `$HOME/.claude/state/mcp-watchdog` — watchdog state, health, and logs. 2. **Keepalive state dir**: `$HOME/.claude/state/mcp-keepalive` — keepalive logs and health. 3. **Reauth state dir**: `$HOME/.claude/state/mcp-reauth` — reauth logs. 4. **Plugin root**: `${CLAUDE_PLUGIN_ROOT}` — used to invoke scripts. 5. **Claude config**: `$HOME/.claude.json` — source of truth for configured MCP servers. If the watchdog state dir does not exist, the watchdog has never run — surface a setup hint on the `status` route. ## Routing table Parse `$ARGUMENTS` and route immediately. First token decides the route. | First arg | Route | | -------------------- | ----------------------------------------------------------------------- | | (empty) / `status` | **Status da...

Details

Author
Lifecycle-Innovations-Limited
Repository
Lifecycle-Innovations-Limited/claude-ops
Created
5 months ago
Last Updated
today
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category