Claude Skill

ca-doctor

Verify the active host install, package, command ownership, enforcement, wrapper self-test, and active-dispatch coverage gap. Read-only.

LLM Mart · 0 points · 16 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download arbiterForge-codeArbiter-plugins_ca-pi_skills_ca-doctor-9957bbf.zip · 1 KB

arbiterforge/codearbiter 145 7 forks AGPL-3.0 Updated 7d ago

Part of arbiterforge/codearbiter — 238 skills

Install

skills CLI npx skills add https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca-pi/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

The /ca-doctor alias has already run the extension's structured Pi doctor report before sending this generated skill. Present the <codearbiter-doctor-report> block below verbatim.
The report inspects, without granting trust: active Git package origin/version, exact Pi CLI and module package identity, stable Pi/Node/Python support, shared-core and bridge paths, command and native-equivalent skill-expansion ownership, child/ambient-marker state, and final wrapper sources.
Its wrapper-self-test row submits only git add --all --dry-run directly to the stored governed Pi bash wrapper. The exact shared-core [H-03] block is healthy and cannot stage files; execution or a different block is unhealthy. This self-test does not traverse Pi's active dispatcher. Do not rerun or respell it.
Its active-dispatch row remains degraded because supported Pi 0.84.1 public extension APIs cannot submit that deterministic call through the active dispatcher. PI-AC-28 remains blocked until supported-version real-host promotion/CI evidence closes the gap.

Remediation ladder

Restart Pi so package resources and final wrappers register in one fresh process.
Reinstall ca-pi from the approved pinned Git tag. For project-local packages, inspect /trust and grant trust only if you accept that source; codeArbiter never grants it.
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 wrapper self-test with different spelling. MUST preserve the degraded active-dispatch diagnosis until supported-version real-host promotion/CI evidence closes PI-AC-28.

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 2.5 KB

---
name: ca-doctor
description: Verify the active host install, package, command ownership, enforcement, wrapper self-test, and active-dispatch coverage gap. 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. The `/ca-doctor` alias has already run the extension's structured Pi doctor report before sending
   this generated skill. Present the `<codearbiter-doctor-report>` block below verbatim.
2. The report inspects, without granting trust: active Git package origin/version, exact Pi CLI and
   module package identity, stable Pi/Node/Python support, shared-core and bridge paths, command and
   native-equivalent skill-expansion ownership, child/ambient-marker state, and final wrapper sources.
3. Its `wrapper-self-test` row submits only `git add --all --dry-run` directly to the stored governed
   Pi bash wrapper. The exact shared-core `[H-03]` block is healthy and cannot stage files; execution
   or a different block is unhealthy. This self-test does not traverse Pi's active dispatcher. Do not
   rerun or respell it.
4. Its `active-dispatch` row remains degraded because supported Pi 0.84.1 public extension
   APIs cannot submit that deterministic call through the active dispatcher. PI-AC-28 remains blocked
   until supported-version real-host promotion/CI evidence closes the gap.

## Remediation ladder

1. Restart Pi so package resources and final wrappers register in one fresh process.
2. Reinstall `ca-pi` from the approved pinned Git tag. For project-local packages, inspect `/trust`
   and grant trust only if you accept that source; codeArbiter never grants it.
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
wrapper self-test with different spelling. MUST preserve the degraded active-dispatch diagnosis until
supported-version real-host promotion/CI evidence closes PI-AC-28.

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.