Check Ruflo's health and summarize system diagnostics, MCP server state, and active agents. Routine checks leave the installation unchanged; an explicit repair request runs the repair command and reports the resulting changes and status.
Diagnose Ruflo health, then report system, MCP server, and active-agent status without changing the installation
Review the instructions the agent will receive before you install.
Use this skill when the user asks for Ruflo health, diagnostics, MCP server state, or active-agent status.
Run these commands in order:
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.
Only when the user explicitly asks to fix or auto-repair the installation, replace the first command with:
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.