hyper-setup
Skill5 starsChanged 48 days agoMITView on GitHub
Diagnose hyperclaude prerequisites and report fixes
In this repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cc-changelogSkill
- codex-changelogSkill
- hyper-autoSkill
- hyper-code-reviewSkill
- hyper-docs-loopSkill
- hyper-docs-reviewSkill
- hyper-docs-syncSkill
- hyper-implement-loopSkill
- hyper-implementSkill
- hyper-interviewSkill
- hyper-memorySkill
- hyper-plan-loopSkill
- hyper-plan-reviewSkill
- hyper-planSkill
- hyper-recapSkill
- hyper-researchSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 10
Run the doctor probe. Parse the JSON it emits and report per-check status plus the overall verdict.
- Very specific: line 39
If ok is true (no hard FAIL): All hard prerequisites met.
- Very specific: line 40
If ok is false (one or more hard FAILs): N hard prerequisite(s) failing — hyperclaude will not work until fixed.
- Very specific: line 47
Do NOT spawn Codex, the bridge (codex-bridge.mjs), or any agent.
- Distinctive: line 48
Do NOT auto-install missing tools or modify env variables.
- Distinctive: line 50
Do NOT treat the Claude Code version WARN as a hard failure.
- Very specific: line 52
No manifest entry needed — Claude Code auto-discovers skills/*/SKILL.md.
- Very specific: line 53
Do not widen allowed-tools beyond Bash(node:*), Read.
≈ “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
hyper-setup
Run the doctor probe. Parse the JSON it emits and report per-check status plus the overall verdict.
Prerequisite probe: !node "${CLAUDE_PLUGIN_ROOT}/scripts/setup-doctor.mjs"
What it checks
The probe emits one JSON line: { ok, checks: [{name, detected, required, status, severity, remediation}] }.
The five checks:
- Node.js >= 18 — severity: hard. hyperclaude's bridge is stdlib Node; versions below 18 are unsupported.
- codex-cli >= 0.130.0 on PATH — severity: hard. Version-floor check only (no capability probe). The bridge spawns
codex exec; the tool must be present and at a known-good version. - git on PATH — severity: hard. The bridge reads git state for slug generation and diff targets.
codex --searchglobal flag (pre-subcommand) — severity: hard. The bridge passes--searchas a global flag before the subcommand on every Codex spawn; codex-cli must acceptcodex --search exec --help(exit 0).- Claude Code >= 2.1.232 — severity: conditional. 2.1.232 is the known-good floor for the background-agent transport
hyper-plan-loop,hyper-implement-loop,hyper-docs-loop, andhyper-auto(which chains hyper-plan-loop → hyper-implement-loop) use to reach their agent. Surfaced, not gated: a below-floor or unknown version (claudeoff PATH, unparseable output) is a WARN that never flips the verdict and blocks nothing — the full research→plan→implement flow works regardless.
Reporting directive
The inline probe above runs automatically; parse the single JSON line it emitted to stdout (do not run it again).
The JSON's shape picks the report. A checks[] array — including the normal ok:false "prerequisites failing" case — gets steps 1–3. Only a probe that itself failed (no parseable JSON, or an {ok:false,error:...} object with no checks[]) gets the step 4 fallback.
For the checks[] path:
- Present a per-check table with columns: Check, Detected, Required, Status. One row per entry in
checks[]. - For every check where
statusis notPASS, print the check'sremediationfield verbatim on its own line, prefixed withFix:. - Conclude with an overall verdict line:
- If
okistrue(no hard FAIL):All hard prerequisites met. - If
okisfalse(one or more hard FAILs):N hard prerequisite(s) failing — hyperclaude will not work until fixed.(N = count ofchecks[]entries withseverity:"hard"andstatus:"FAIL"). - The Claude Code version WARN must never flip the overall verdict to fail.
- If
- Error fallback — print exactly this, and nothing that reads as a pass:
Prerequisite probe could not complete: <error or "no parseable output">. hyperclaude prerequisites are UNKNOWN — re-run /hyperclaude:hyper-setup or run the doctor script directly.
Anti-patterns
- Do NOT spawn Codex, the bridge (
codex-bridge.mjs), or any agent. This skill only runs the doctor probe. - Do NOT auto-install missing tools or modify env variables. This skill is read-only; report-and-advise only.
- The
Bash(node:*)filter permits arbitrary node scripts, so never edit this skill to invoke anything beyond the doctor probe — read-only is prompt-enforced, not tool-enforced. - Do NOT treat the Claude Code version WARN as a hard failure.
- No npm dependencies.
- No manifest entry needed — Claude Code auto-discovers
skills/*/SKILL.md.disable-model-invocation: truekeeps this skill explicit-invoke-only (/hyperclaude:hyper-setup); it is never auto-triggered by its description. - Do not widen
allowed-toolsbeyondBash(node:*), Read.
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.

