Run moflo's Healer (`flo healer`, alias for `flo doctor`) from inside the Claude session. Audit-only by default; pass `--fix` to apply auto-repairs, `-c <component>` for a single check. Use when something feels off (missing moflo.yaml, daemon dead, statusline empty, hooks not firing) or as a periodic health check. Distinct from Claude Code's built-in `/doctor`, which diagnoses Claude Code itself, not moflo.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Thin wrapper around the flo healer CLI. All check + fix logic lives in the CLI; this skill just shells out, surfaces results in-thread, and gives one-line follow-up nudges.
Arguments: $ARGUMENTS
Memory first (gate requirement):
mcp__moflo__memory_search { query: "doctor healer fix moflo.yaml gate hook wiring", namespace: "guidance" }
Run the CLI with the user's arguments passed through:
npx moflo healer --json $ARGUMENTS
--fix → CLI runs auto-repairs after the audit.-c <component> → restricts to one check.--json so output is machine-parseable.Surface the JSON in-thread. Group by status:
✓ N passing (count only)⚠ warnings — list name: message; flag with [auto-fixable] when the result has a fix field✗ failures — same--fix mode, read fixesApplied[] from the JSON payload and list {name, applied} per entry — applied=true → "fixed", applied=false → "needs manual action". The results[] array is post-fix state (re-evaluated), so report the final status.--install was passed, surface claudeCodeInstall.installed from the payload.--kill-zombies was passed, surface zombieScan.killed / zombieScan.found from the payload.Nudge based on what changed. Only mention next steps for state that actually changed:
Statusline should refresh within ~5s.moflo.yaml created → Review the new defaults at the project root before your next deep run.Restart Claude Code so the new SessionStart hook fires next launch.Run /healer --fix to repair.--help and src/cli/commands/doctor-* are the source of truth.flo doctor directly — use the healer alias for thematic consistency. They're equivalent CLI-side./doctor command that diagnoses Claude Code itself. This skill (/healer) diagnoses moflo, not Claude Code. The two are complementary, not duplicates. The healer rolls in the user-actionable parts of claude doctor (Claude Code version freshness vs npm latest) into its own Claude Code CLI check; the rest of claude doctor is a TUI on current releases and must be run interactively if you need its full report.flo doctor --help — full flag/component list/eldar — broader project-setup audit; consults the Healer as one inputまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Turn a vague idea into a concrete, actionable spec through a short Socratic dialogue, then hand the result off to an existing moflo surface — a /flo ticket, a spell, or memory. Use BEFORE you have a defined unit of work, when the goal is still fuzzy.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold new spell step commands and connectors. Use when building new step commands for spells or extending the spell engine with new capabilities. Connectors are for new I/O transport types OR platforms requiring complex multi-step interaction (e.g., browser-based automation).
日本語の概要は準備中です。原文の説明を表示しています。
Alias for /flo-simplify — see that skill's description.
日本語の概要は準備中です。原文の説明を表示しています。
Structured multi-hop web research with explicit confidence gating — plan the inquiry, search (WebSearch/WebFetch), score your own confidence, and keep digging until the answer is well-supported or a hop cap is hit, then emit a cited synthesis. Learns across sessions by storing each research case to memory and reusing prior strategies. Use when a question needs more than one search — comparisons, current-best-practice questions, anything where a single lookup leaves you unsure.
日本語の概要は準備中です。原文の説明を表示しています。
Consult the Eldar — audit a project's moflo + Claude Code setup for portable, high-leverage gaps and guide remediation. Default mode is read-only audit with severity-ranked findings; --fix presents an interactive triage menu and walks the user through each chosen fix (healer, missing CLAUDE.md, sparse guidance, hook/MCP wiring, empty memory namespaces, stack→guidance gaps). Use when starting in a new project, when Claude feels lost or inefficient, when guidance/CLAUDE.md is sparse, or as a periodic health check.
日本語の概要は準備中です。原文の説明を表示しています。
Run /fl on a ticket with moflo's three standing considerations loaded first — cross-platform (Rule
日本語の概要は準備中です。原文の説明を表示しています。