| name | harness-slim |
| description | Audit and reduce a live multi-runtime agent harness after adoption. Use for
installed skill/plugin parity, cold-start context, routing overlap, telemetry,
or human-attention load. Produces a reversible proposal; it does not mutate
the harness.
|
| reads | [{"repo":"AGENTS.md"},{"repo":"CLAUDE.md"},{"cli":"git"},{"cli":"codex"},{"cli":"claude"}] |
| writes | [{"cli":"stdout"}] |
| domain | shared |
| classification | hybrid |
| user-invocable | true |
Harness Slim
This is the post-adoption harness evaluator. gatekeeper decides whether
an external artifact is safe to adopt; review checks a code diff;
harness-slim compares the live source, installation, runtime, context, and
attention surfaces after adoption.
Contract
- Audit read-only. Propose before any move; execution routes through
careful
and the host's normal issue/worktree flow.
- Treat responsibility overlap as the prune signal. Counts and usage are
supporting evidence, never deletion authority.
- Keep
actual_invocation, dispatch_selection, and load_proxy separate.
A skill-file read is load evidence, not invocation.
- Preserve trust, permission, data-loss, and external-write gates unless a
replacement proves the same behavior.
Audit
- Read the host contract and machine-state documentation. Resolve the
authoritative source manifest, installed registrations/caches, cold-start
adapters, available doctor commands, and telemetry. Missing paths remain
named evidence gaps; do not invent defaults.
- Run read-only doctors first. Report source truth, installed truth, and live
runtime truth independently; one green surface cannot mask another red one.
- Inventory what hosts actually register. Marketplace/catalog availability,
unregistered files, remote tools, and optional overlays are separate
surfaces.
- Normalize usage by event semantics and coverage. Zero-use pruning requires
at least 30 days, 20 eligible opportunities for that skill, and verified
outcome coverage. Lifetime counters cannot prove a windowed zero.
- Audit context. Measure content actually injected at cold start and classify
each instruction as always-on, deferred, or task-local. Tool
recipes, examples, and domain detail default to deferred loading. Name one
owner and absorber for every duplicate responsibility.
- Audit attention. Long-running or parallel routes need a checkable exit,
plateau/budget bound, quiet background behavior, and aggregated reporting.
Preserve one foreground judgment lane. Resolve unknowns before long
execution; use independent maker/verifier contexts only when subjective or
high-risk output lacks a deterministic check.
- Classify each surface exactly once: Keep, Slim, Resource,
Maintainer-only, Overlay, or Retire. A major model change earns
paired with-skill/without-skill fixtures before retirement.
Output
Harness slim
Core health: green | red
Runtime surface: source / installed / live
Telemetry: event kinds, coverage, eligible sample
Context: always-on / deferred / task-local, bytes or observed tokens
Attention: foreground lane, background exits, aggregation, verifier policy
Keep / Slim / Resource / Maintainer / Overlay / Retire: owner + evidence
Backups: required paths for a later move
Verification: commands + observed results
Stop after the proposal. A later execution must preserve backups, rerun every
red-capable doctor, and prove cold-start parity.
