Skip to content

heal-skill

Check or repair structural hygiene in AgentOps skill packages. Triggers: "heal skill", "repair skill hygiene", "audit skill structure", "check skill package".

1,154
installs
0 up / 0 down, score 0.00
votes
450
repo stars
Updated
less than a month ago
In the catalog since
5 Oct 2026
From
boshu2/agentops
AI & Agents
Get it through your agent npx skills add boshu2/agentops@heal-skill

Skill instructions

Rendered from the published SKILL.md, 70 lines.

/heal-skill — Check one or more skill packages

heal-skill is a specialist hygiene tool. It reports structural defects in canonical source skills and generated Codex twins. With --fix, it repairs only owned projections through their generators. It does not schedule work, operate Git, validate a software candidate, or decide what happens after a failure.

Inputs

bash skills/heal-skill/scripts/heal.sh --check [skills/<slug> ...]
bash skills/heal-skill/scripts/heal.sh --check --strict [skills/<slug> ...]
bash skills/heal-skill/scripts/heal.sh --fix [skills/<slug> ...]

Every explicit target must be a real, direct child of skills/ or skills-codex/. Missing paths, traversal, and symlink spellings are rejected.

Procedure

  1. Resolve and contain all requested target directories.
  2. Parse each SKILL.md frontmatter.
  3. Check the path/name match, description, API version, disposition metadata, and linked local references.
  4. Print every finding once.
  5. In --fix mode only, regenerate metadata-owned projections and scoped Codex twins, then stop.

--check is read-only. --strict makes any finding produce exit 1. A failed fix is returned to the caller; the skill does not retry or select another action.

Deep content audit

The optional read-only content audit is:

bash skills/heal-skill/scripts/audit.sh [--strict] [--json <path>] skills/<slug>

It combines the structural result with deterministic authoring checks and an advisory quality score. It is not the core Validate phase, does not write a verdict.v2, and has no delivery authority. Check definitions live in audit-checks.md; density scoring is described in context-density-checks.md.

Output

Structural findings are printed as:

[FINDING_CODE] skills/example: concrete explanation

Deep audit JSON conforms to audit-report.json. The caller owns any subsequent edit or invocation.

Checks

  • Check mode never mutates files.
  • Fix mode changes only an explicit source target and its owned projections.
  • A second identical fix is idempotent.
  • Generated Codex parity follows codex-parity.md.
  • Remaining non-fixable findings stay explicit.

Related executable specifications