doctor
Skill18 starsChanged 3 months agoMITView on GitHub
Health check for ginnie-agents — verifies prerequisites, environment, hooks, listener, Docker image, agents, memory caps, and disk. Use when the user says "doctor", "health check", "check setup", "is everything ok", or after running setup/update.
- Reads credentials
- Sends data out
85 other projects use a version of this.
Adopted by
Most recently taken up by
- aaroncohn/babysittertheir own version, first seen Nov 16, 2026
- Yomudogly/oh-my-agytheir own version, first seen Nov 16, 2026
- timursafiullin/aodtheir own version, first seen Nov 15, 2026
- mkritter3/codex-paired-superpowerstheir own version, first seen Nov 15, 2026
- dcamunas/model-routertheir own version, first seen Nov 15, 2026
- Noah-OS/longhaultheir own version, first seen Nov 15, 2026
Used with
Projects with it also use uninstall, cancel 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.
AnthropicSkilluninstall
Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.
Also in 6 projects that use this
woosikkimSkillcancel
Clear any stale OMC-Slim state
Also in 4 projects that use this
ibahgatSkillhud
Control omi visual HUD profile and keep status output readable in normal, compact, or hidden mode.
Also in 3 projects that use this
ibahgatSkillralplan
Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.
Also in 3 projects that use this
QinghongLinSkilleditor
Read analyst.json and detective.json, make all editorial decisions — what the blog argues, which findings matter, narrative arc and section structure. No visual design. Outputs editor.md (prose) and editor.json (structure with edt_xx IDs).
Also in 3 projects that use this
BlockSkillopen
Open markdown documents in Penpal for collaborative review. Use when you want a human to review a document, plan, or research artifact.
Also in 3 projects that use this
- +1 more from ibahgat
Other versions85 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 85
- Yeachan-Heo/oh-my-codex★ 34ksame name
- jihe520/MathModelAgent★ 6.2ksame name
- spotify/portal-ai-plugins★ 2.8ksame name
- fakechris/obsidian_vault_pipeline★ 173same name
- NoobyGains/godmode★ 120same name
- Rich627/whatsapp-claude-plugin★ 114same name
- bluzir/claude-code-design★ 102same name
- jjanczur/tyran★ 79same name
- svy04/ballast★ 73same name
- Hainrixz/agente-pagokit★ 68same name
75 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 repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- create-agentSkill
- logsSkill
- manage-known-usersSkill
- manage-routinesSkill
- manage-work-hoursSkill
- setupSkill
- setup-watcherSkill
- update-frameworkSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 64 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Run from repo root.
- Distinctive: line 22
If exit code is non-zero, do NOT continue to the contextual checks below until the script's failures are addressed — they're foundational.
- Very specific: line 49
Only relevant when the operator is on Option A (CLAUDE_CODE_OAUTH_TOKEN).
- Very specific: line 57
If mode A: CLAUDE_CODE_OAUTH_TOKEN from claude setup-token lasts ~1 year.
- Very specific: line 68
If any are >330 days old, recommend claude setup-token and refreshing .env + the tracker file.
- Distinctive: line 72
If the script exited 0 and Slack is reachable, summarize: "Healthy — N agents online, all Slack tokens valid, no memory caps near limit."
- Distinctive: line 74
If anything failed, list the failures + their suggested fixes in priority order:
“Common” is measured: kept by at least 6 in 10 of the 64 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Doctor — Health Check
The mechanical checks live in scripts/doctor.sh so they run identically every time, with or without Claude. This skill runs the script and adds the contextual checks (Slack reachability, token-age awareness, claude setup-token rotation hint) that benefit from a per-installation read.
Run from repo root.
Step 1 — Run the script
bash scripts/doctor.shExit code: 0 = all green, 1 = at least one failure.
The script's output is already human-readable (✓/✗/!) with fix suggestions. Show it to the user as-is. Don't paraphrase.
If exit code is non-zero, do NOT continue to the contextual checks below until the script's failures are addressed — they're foundational. Tell the user exactly what to fix.
Step 2 — Contextual: Slack reachability
The script doesn't hit Slack (it's a mechanical, network-free check). If the user wants a deeper verification, do this for each agent that has credentials.json:
for d in agents/*/; do
[ -d "$d" ] || continue
agent="$(basename "$d")"
token="$(jq -r .slack_bot_token "$d/credentials.json" 2>/dev/null)"
[ -n "$token" ] && [ "$token" != "null" ] || continue
result=$(curl -s -X POST https://slack.com/api/auth.test \
-H "Authorization: Bearer $token" | jq -r '"\(.ok) \(.error // "—") \(.team // "—")"')
echo " $agent: $result"
doneInterpret:
true — <Workspace Name>→ token goodfalse invalid_auth→ token revoked or wrong; regenerate at the agent's Slack app OAuth & Permissions page, updateagents/<n>/credentials.json,pm2 restart ginnie-agents-listenerfalse token_revoked→ same fixfalse account_inactive→ user removed from workspacefalse ratelimited→ wait, retry
Step 3 — Contextual: token age awareness
Only relevant when the operator is on Option A (CLAUDE_CODE_OAUTH_TOKEN). Skip this step for Option B (ANTHROPIC_API_KEY) — API keys don't expire on a fixed schedule, so there's nothing for the framework to count days against.
Detect mode:
grep -qE '^ANTHROPIC_API_KEY=sk-ant-' .env && echo "mode=B (skip token-age check)" || echo "mode=A (run token-age check)"If mode A: CLAUDE_CODE_OAUTH_TOKEN from claude setup-token lasts ~1 year. There's no API to introspect issuance date from outside the token itself. If a memory/token-issued-at.txt file exists in any maintenance agent's memory dir, surface its age:
for f in agents/*/memory/token-issued-at.txt; do
[ -f "$f" ] || continue
d=$(cat "$f")
age=$(( ( $(date +%s) - $(date -j -f '%Y-%m-%d' "$d" +%s 2>/dev/null || date -d "$d" +%s) ) / 86400 ))
echo " $(dirname "$(dirname "$f")") tracker: token aged $age days (cap ~365)"
doneIf any are >330 days old, recommend claude setup-token and refreshing .env + the tracker file.
Step 4 — Final summary
If the script exited 0 and Slack is reachable, summarize: "Healthy — N agents online, all Slack tokens valid, no memory caps near limit."
If anything failed, list the failures + their suggested fixes in priority order:
.env/ token issues (foundation)- Hooks (data integrity)
- Listener / PM2 (runtime)
- Per-agent issues (specific to one agent)
- Memory caps (background concern)
- Disk (background concern)
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.

