Claude Skill

ca-doctor

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

LLM Mart · 0 points · 16 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download arbiterForge-codeArbiter-plugins_ca-codex_skills_ca-doctor-bc9c216.zip · 0 KB
Part of arbiterforge/codearbiter — 238 skills

Install

skills CLI npx skills add https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca-codex/skills/ca-doctor
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install arbiterforge-codearbiter@llmmart
Git git clone https://github.com/arbiterForge/codeArbiter.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole arbiterforge/codearbiter collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

$ca-doctor — install health

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.

Flow

  1. 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.
  2. 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.

Remediation ladder

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

When NOT to use

  • Scaffold state only → $ca-init --check.
  • Project progress, not install health → $ca-status.

Hard gate

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.

For an arbiter-enabled repository, the mechanical report treats the Git backstop as healthy only after exact managed-shim and live-enforcer validation, plus a harmless selected-Git git hook run pre-push probe with empty input. It never executes a foreign hook.

Files (codearbiter)
  • SKILL.md 1.6 KB
    ---
    name: ca-doctor
    description: Verify the active host install, package, command ownership, enforcement, and harmless live-fire probe. Read-only.
    argument-hint: (none)
    ---
    
    # $ca-doctor — install health
    
    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.
    
    ## Flow
    
    1. 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.
    2. 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**.
    
    ## Remediation ladder
    
    1. Restart Codex so hooks register at session start.
    2. Remove and re-add `ca-codex@codearbiter`, then approve the changed hook set in `/hooks`.
    3. If dormancy was intended, `$ca-init` opts the repository in.
    
    ## When NOT to use
    
    - Scaffold state only → `$ca-init --check`.
    - Project progress, not install health → `$ca-status`.
    
    ## Hard gate
    
    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.
    
    For an arbiter-enabled repository, the mechanical report treats the Git backstop as healthy only
    after exact managed-shim and live-enforcer validation, plus a harmless selected-Git
    `git hook run pre-push` probe with empty input. It never executes a foreign hook.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related