agent-shims

Before asking, read User Questions.

Agent Shims

After user intervention or repeated invocation, follow Resume And Re-entry: complete selected action's verification and diagnostic instructions below. This manager keeps its non-artifact lifecycle; it doesn't skip its closing checks or replace final explanation with raw JSON.

This is experimental lifecycle tool. Installing authenticated standalone agent TOML does not prove that active collaboration interface can select that custom profile. A task name or child path matching role name is not proof. Use installed shims only when runtime exposes explicit custom-agent selector and observed child metadata plus verifier output prove selection; otherwise use blank-agent role-card injection.

Accept exactly one action: doctor, status, install, or remove. Reject missing, extra, or unknown arguments without writes.

Any follow-up question follows User Questions: put accepted action names or required input format in the permitted native control after showing context; use plain chat only when no permitted native control is suitable. Preserve the manager's exact-digest removal confirmation syntax; never substitute a generic yes/no response for that digest-bound input. The blocked install action still requires no approval prompt.

Locate ../../scripts/manage_role_agents.py relative to this installed SKILL.md. Run it with current Python 3.10+ interpreter and selected action. Never copy manager, resolve it through source checkout, or edit generated agent files directly.

• doctor: run read-only live prerequisite check, render its JSON result for person.
• status: run read-only health and installed-roster summary, render its JSON result for person.
• install: report stable platform block. Never request approval; no new shim plan or write is allowed.
• remove: use same exact-digest flow to remove every intact managed shim. Never delete by filename prefix or marker alone. On failure, apply the same per-exit-code recovery guidance listed below for doctor and status — it applies to remove's failure modes too.

Preserve manager's exit contract: 0 success/converged, 2 usage, 3 cancelled, 4 drift/conflict, 5 prerequisite blocked, 6 untrusted state, 7 internal/recovery failure. Never retry mutating action after codes 4, 6, or 7; report evidence, keep files untouched.

For doctor and status, never return only raw JSON or generic safety label:

1. Start with plain-English explanation of whether shims are usable and what needs attention. Then give Healthy, Degraded, or Blocked, followed by first non-pass check and its exact detail; never expose raw diagnostic JSON as whole answer.
2. List every other non-pass check once, then summarize state, targets, recovery, namespace candidates.
3. State No files changed.
4. Give narrow safe next step. For package or active-package failures, refresh or reinstall Codex Rig, start fresh session. For executable failures, report selected path, rerun from fresh session with stable Python and Codex selection. For permission, owner, type, or link failures, inspect only named path, verify its metadata before changing anything. For corrupt, inconsistent, modified, or foreign evidence, back it up, never adopt, edit, or delete it automatically. For recognized recovery residue, use remove, review its authenticated approval digest.

Never recommend recursive chmod, chown, deletion, or link replacement from diagnostic alone. On POSIX systems, a protected agent target may be readable by other users, but it must be owned by current user, have no group/world write or special permission bits; private lifecycle state remains exact mode 0700. Not applicable on Windows, where remove is platform-blocked.

After successful install or removal, tell user to start fresh Codex session. Thin shims intentionally depend on installed plugin cache; uninstalling plugin makes remaining shims unavailable until safely removed or reinstalled.