Diagnose Ruflo health, then report system, MCP server, and active-agent status without changing the installation
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add ruvnet/ruflo --skill ruflo-status --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ruflo Status?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ruvnet-ruflo-status)More formats (shields.io, HTML) on the badges page.
---
name: ruflo-status
description: Diagnose Ruflo health, then report system, MCP server, and active-agent status without changing the installation
argument-hint: "[--fix]"
allowed-tools: Bash(npx *)
---
# Ruflo status
Use this skill when the user asks for Ruflo health, diagnostics, MCP server
state, or active-agent status.
## Default read-only workflow
Run these commands in order:
```bash
npx @claude-flow/cli@latest doctor
npx @claude-flow/cli@latest status
```
Summarize the diagnostics and status together. Do not repair, reset, start,
stop, install, or otherwise change anything during the default workflow.
## Explicit repair workflow
Only when the user explicitly asks to fix or auto-repair the installation,
replace the first command with:
```bash
npx @claude-flow/cli@latest doctor --fix
npx @claude-flow/cli@latest status
```
Report what the repair changed and the resulting status. Never infer
authorization for `doctor --fix` from a request to check or diagnose Ruflo.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
