healthcheck
Skill0 starsChanged 4 months agoMITView on GitHub
Verify the assistant's memory, structure, and harness wiring are all in working order — counts indexed memories, checks rules/ and contexts/ are present, checks whether the knowledge graph is stale, and confirms which harness files are correctly symlinked. Use when the user asks "are you active?", "is your memory loaded?", "healthcheck", "are you working?", or wants a status/diagnostic of the assistant itself.
38 other projects use a version of this.
Adopted by
Most recently taken up by
- grainulation/grainulatortheir own version, first seen Nov 3, 2026
- QVerisAI/QVerisBottheir own version, first seen Nov 1, 2026
- AlekseiUL/heisenberg-team-GPTtheir own version, first seen Nov 1, 2026
- AlekseiUL/heisenberg-teamtheir own version, first seen Nov 1, 2026
- OpenClawAndroid/openclaw-android-assistanttheir own version, first seen Oct 17, 2026
- foxl-ai/skillstheir own version, first seen Oct 15, 2026
Used with
Projects with it also use taskflow-inbox-triage, node-connect and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AtomicBot-aiSkilltaskflow-inbox-triage
Also in 6 projects that use this
hkyutongSkillnode-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.
Also in 18 projects that use this
molt-botSkilldiscord-e2e
Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and Gateway evidence from manual user interactions.
Also in 10 projects that use this
molt-botSkillopenclaw-repair-sweep
Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.
Also in 10 projects that use this
clawdbotSkillopenclaw-performance
Performance work in OpenClaw: a slow or heavy flow (latency, CPU, memory, SQL, RPC, renders), writing or reviewing a perf PR, or adding a cache. Count the work, delete waste first, cache last.
Also in 7 projects that use this
clawdbotSkillplugin-sdk-impact
Count Plugin SDK consumers across live ClawHub releases and bundled OpenClaw plugins before deprecation, removal, or behavior changes; supports public release-date filters.
Also in 7 projects that use this
- +2 more from molt-bot
Other versions38 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 38
- moltbot/clawdbot★ 394ksame name
- steipete/warelay★ 394ksame name
- steipete/clawdis★ 394ksame name
- moltbot/moltbot★ 394ksame name
- clawdbot/clawdbot★ 394ksame name
- openclaw/openclaw★ 394ksame name
- molt-bot/clawdbot★ 391ksame name
- spinabot/brigade★ 11ksame name
- the-open-agent/openagent★ 5.7ksame name
- casibase/casibase★ 5.7ksame name
28 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- background-removeSkill
- brainSkill
- dev-localSkill
- logo-designerSkill
- parce-squadSkill
- ultra-modeSkill
The file
Files
Healthcheck
A quick, silent self-check of the assistant's setup. Run the checks in parallel, don't narrate them, then report a short status table.
What to check
(a) Memory index
wc -l memory/MEMORY.md
ls memory/*.md | grep -v -e MEMORY.md -e _template.md | wc -lConfirm memory/MEMORY.md exists and is readable. Count entries (lines starting with - [) and compare against the number of .md files in memory/ (excluding MEMORY.md and _template.md) — flag it if the index is missing files or has stale entries pointing at deleted ones.
(b) Structure present
ls rules/ contexts/Confirm both directories exist and are non-empty.
(c) Graph freshness
ls -t memory/*.md | grep -v -e MEMORY.md -e _template.md | head -1 | xargs stat -f "%m %N"
stat -f "%m %N" memory/graph.json 2>/dev/nullCompare the newest memory file's mtime against memory/graph.json's mtime. If any memory file is newer than the graph (or graph.json doesn't exist yet), report it as stale and suggest:
node skills/brain/build-graph.mjs(d) Harness files
for f in CLAUDE.md AGENTS.md .github/copilot-instructions.md; do
if [ -L "$f" ]; then
echo "$f -> symlink -> $(readlink "$f")"
elif [ -e "$f" ]; then
echo "$f -> exists but NOT a symlink"
else
echo "$f -> missing"
fi
doneEach of these should exist and be a symlink pointing at ASSISTANT.md. Flag any that are missing or that exist as real (non-symlink) files — the latter means edits to them won't propagate to ASSISTANT.md.
Output
Report a short status table, one row per check, then a one-line verdict:
| Check | Status | Detail |
| Memory index | OK / gap | N memories indexed, M files on disk |
| rules/ + contexts/ | OK / missing | — |
| Graph freshness | OK / stale | newest memory vs graph.json mtime |
| Harness symlinks | OK / gap | which files are missing or not symlinks |
Verdict: Active (all OK), Partial (memory + structure OK, something else off), or Inactive (memory or structure broken). If something is stale or missing, name the exact fix command instead of just flagging it.
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.

