healer
Skill19 starsChanged 3 months agoMITView on GitHub
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.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- communeSkill
- connector-builderSkill
- distillSkill
- divineSkill
- eldarSkill
- flflSkill
- flo-simplifySkill
- floSkill
- floSkill
- guidanceSkill
- luminariumSkill
- meditateSkill
- memory-optimizationSkill
- memory-patternsSkill
- memory-teamSkill
- memory-worktreeSkill
- optimize-learningsSkill
- perf-auditSkill
- publishSkill
- quickenSkill
- reasoningbank-intelligenceSkill
- reset-epicSkill
- spell-builderSkill
- spell-scheduleSkill
- test-gapsSkill
- vector-searchSkill
- verifySkill
- wardSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Always include --json so output is machine-parseable.
- Very specific: line 33
If --fix mode, read fixesApplied[] from the JSON payload and list {name, applied} per entry — applied=true → "fixed", applied=false → …
- Very specific: line 34
If --install was passed, surface claudeCodeInstall.installed from the payload.
- Very specific: line 35
If --kill-zombies was passed, surface zombieScan.killed / zombieScan.found from the payload.
- Distinctive: line 37
Nudge based on what changed: Only mention next steps for state that *actually* changed:
- Very specific: line 46
Don't: call flo doctor directly — use the healer alias for thematic consistency.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/healer — moflo Installation Healer
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
Procedure
- 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- No args → audit-only.
--fix→ CLI runs auto-repairs after the audit.-c <component>→ restricts to one check.- Always include
--jsonso output is machine-parseable.
- Surface the JSON in-thread. Group by status:
✓ N passing(count only)⚠ warnings— listname: message; flag with[auto-fixable]when the result has afixfield✗ failures— same- If
--fixmode, readfixesApplied[]from the JSON payload and list{name, applied}per entry — applied=true → "fixed", applied=false → "needs manual action". Theresults[]array is post-fix state (re-evaluated), so report the final status. - If
--installwas passed, surfaceclaudeCodeInstall.installedfrom the payload. - If
--kill-zombieswas passed, surfacezombieScan.killed/zombieScan.foundfrom the payload.
- Nudge based on what changed. Only mention next steps for state that actually changed:
- Daemon restarted →
Statusline should refresh within ~5s. moflo.yamlcreated →Review the new defaults at the project root before your next deep run.- Hook wiring repaired →
Restart Claude Code so the new SessionStart hook fires next launch. - In audit-only mode with auto-fixable issues →
Run /healer --fix to repair.
- Daemon restarted →
Rules
- Don't re-document checks or fixes here. The CLI's
--helpandsrc/cli/commands/doctor-*are the source of truth. - Don't call
flo doctordirectly — use thehealeralias for thematic consistency. They're equivalent CLI-side. - Don't swallow non-zero exit codes silently — surface them in the summary.
- Note for users: Claude Code has its own built-in
/doctorcommand 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 ofclaude doctor(Claude Code version freshness vs npm latest) into its ownClaude Code CLIcheck; the rest ofclaude doctoris a TUI on current releases and must be run interactively if you need its full report.
See Also
flo doctor --help— full flag/component list/eldar— broader project-setup audit; consults the Healer as one input
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

