Ca Doctor

arbiterforge/ca-doctor

Verify the active host install, package, command ownership, enforcement, and harmless live-fire probe. Read-only.

338 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

138

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/arbiterForge/codeArbiter --skill ca-doctor

5 sections, as written by the author

Silent dormancy is the worst failure shape this plugin has: the gates look installed but never fire.

This command proves the active host is healthy and reports every non-OK finding with an exact

remediation.

Resolve the plugin root from this loaded skill path, then run its hooks/doctor.py with Python 3

and present the report verbatim. Do not try an empty plugin-root environment variable first.

In an arbiter-enabled repo, attempt git add --all --dry-run via the shell tool. [H-03] means

hooks are firing; execution means CRITICAL: gates dormant.

Restart Codex so hooks register at session start.
Remove and re-add ca-codex@codearbiter, then approve the changed hook set in /hooks.
If dormancy was intended, $ca-init opts the repository in.

Read-only. MUST NOT create markers, stage files, grant trust, weaken a block, or retry the live-fire

probe with different spelling. MUST surface a failed probe as CRITICAL, never as a footnote.

Copy the folder

Take arbiterforge/ca-doctor from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.