superskills-doctor
Skill12 starsChanged 4 months agoMITView on GitHub
Diagnose a superskills install WITHOUT changing anything: install kind, which skills are linked, VERSION vs the plugin manifests, gstack (real clone or vendor stopgap), bun and optional tools. Use when a skill is missing or won't trigger, a pull or upgrade looks stale, setup failed, or the user asks whether superskills is healthy, ready, or installed correctly. Read-only: it never installs, pulls, or re-runs setup — to fix things use /superskills-upgrade.
- Pipes a download into a shell
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Read-only health check. Report what is, never repair it.
- Very specific: line 27
Never mutate: Do not run ./setup, git pull, git reset, curl … | bash, bun install, or any login.
- Very specific: line 76
If it prints DOCTOR=missing, that is itself the finding: report Repo: blocked with the reinstall command below and stop.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
/superskills-doctor
Read-only health check. Report what is, never repair it.
Rules
- Never mutate. Do not run
./setup,git pull,git reset,curl … | bash,bun install, or any login. If the user wants the fix, name the command from the table's "next action" column or point at/superskills-upgrade. - Never claim readiness the script did not. The verdict is the script's verdict. "blocked" or "unverified" means not ready, even if most rows are fine.
- Report evidence, not impressions. Reproduce the table; do not summarise rows away or add checks you did not run.
Steps
Step 1: Locate and run the doctor (one command)
The script lives in the superskills repo at scripts/doctor.sh. Find the repo, in
order: the directory this skill was loaded from (if your host told you this skill's
base directory, put it in SKILL_DIR on the first line), the Claude Code plugin
root, then this skill's ./setup symlink for Claude Code, Codex or OpenCode —
never the working directory. Locate and run it in a single Bash call: separate
calls do not share shell variables, so a path found in one call is gone in the next.
SKILL_DIR="${SKILL_DIR:-}" # set to this skill's base directory when the host provides it
case "$SKILL_DIR" in /*) : ;; *) SKILL_DIR="" ;; esac # only an absolute path is trusted, never resolved against the cwd
ROOT=""
for cand in "${SKILL_DIR:+$SKILL_DIR/../..}" "${CLAUDE_PLUGIN_ROOT}"; do
[ -n "$cand" ] && [ -f "$cand/scripts/doctor.sh" ] && { ROOT="$(cd "$cand" && pwd -P)"; break; }
done
if [ -z "$ROOT" ]; then
for probe in "$HOME/.claude/skills/superskills-doctor/SKILL.md" \
"$HOME/.codex/skills/superskills-doctor/SKILL.md" \
"$HOME/.config/opencode/skills/superskills-doctor/SKILL.md" \
"$HOME/.zcode/skills/superskills-doctor/SKILL.md"; do
# Only a link that resolves to a real file counts; never fall back to the cwd.
[ -L "$probe" ] || continue
real="$(readlink -f "$probe" 2>/dev/null || perl -MCwd=realpath -e 'print realpath($ARGV[0])' "$probe")"
if [ -n "$real" ] && [ -f "$real" ]; then
ROOT="$(cd "$(dirname "$real")/../.." 2>/dev/null && pwd -P)"
[ -f "$ROOT/scripts/doctor.sh" ] && break
ROOT=""
fi
done
fi
if [ -n "$ROOT" ] && [ -f "$ROOT/scripts/doctor.sh" ]; then
echo "DOCTOR=$ROOT/scripts/doctor.sh"
bash "$ROOT/scripts/doctor.sh" "$@"
else
echo "DOCTOR=missing"
fiIf it prints DOCTOR=missing, that is itself the finding: report Repo: blocked
with the reinstall command below and stop. Do not improvise checks.
git clone https://github.com/ariadoss/superskills.git ~/.claude/skills/superskills && cd ~/.claude/skills/superskills && ./setupTo inspect an install that is not the current user's (a container, a test tree,
a colleague's copy), run the same block with the flags appended to the
bash "$ROOT/scripts/doctor.sh" line: --root <superskills-checkout> --home <home-dir>.
To call the script directly later, use the path from the DOCTOR= line.
Step 2: Read the output
The script prints a markdown table (Check | Status | Evidence / next action)
and a final Verdict: line. Statuses:
| Status | Meaning |
| ready | passed |
| warning | usable; something optional is off |
| blocked | a required piece is missing or broken — the row says what to run |
| unverified | the probe could not run (e.g. no claude CLI) — unknown, not fine |
Step 3: Report
Return the table verbatim, then the verdict, then one line per non-ready row naming the next action from that row. Say plainly:
- Verdict: ready → "superskills is ready."
- ready with warnings → ready, and list the warnings.
- blocked → "Not ready" and the blocked rows first. The usual fix is
./setupfrom the repo, or/superskills-upgrade; offer it, do not run it. - unverified → say readiness is unknown and which probe could not run.
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- a11ySkill
- articleSkill
- basic-reviewSkill
- cache-strategySkill
- clean-codeSkill
- cli-for-agentSkill
- content-writerSkill
- daily-qaSkill
- dbmap-auto-offSkill
- dbmapSkill
- db-optimizeSkill
- debugSkill
- defenseSkill
- diff-walkthroughSkill
- evalSkill
- executing-plansSkill
- finish-branchSkill
- fuzzSkill
- handoffSkill
- humanizeSkill
- iac-scanSkill
- kb-advisorSkill
- minimalist-reviewSkill
- pentestSkill
- perf-profileSkill
- playwrightSkill
- pricingSkill
- qa-fullSkill
- quota-resilienceSkill
- subagent-driven-developmentSkill
- superskills-upgradeSkill
- tapestrySkill
- tddSkill
- test-coverageSkill
- validate-ideaSkill
- verifySkill
- web-perfSkill
- worktreesSkill
- write-planSkill
- youtubeSkill
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.

