Skip to content

Skill Lifecycle

Connor edited this page Jul 3, 2026 · 2 revisions

Skill Lifecycle

A useful skill environment needs maintenance. Too many stale, overlapping, or noisy skills reduce agent quality.

Audit

Audit installed skills for Codex:

python scripts/audit_skills.py audit --dest "$HOME/.agents/skills"

Audit installed skills for Claude Code:

python scripts/audit_skills.py audit --dest "$HOME/.claude/skills"

Disable

Disable a noisy or unused skill without deleting it:

python scripts/audit_skills.py disable <skill-name> --dest "$HOME/.agents/skills"

Quarantine

Quarantine suspicious skills:

python scripts/audit_skills.py quarantine <skill-name> --dest "$HOME/.agents/skills"

Restore

Restore a disabled skill:

python scripts/audit_skills.py restore <skill-name> --dest "$HOME/.agents/skills"

Prune

Dry-run first:

python scripts/audit_skills.py prune --older-than-days 180 --dry-run --dest "$HOME/.agents/skills"

Then prune only when the removal set is clearly correct.

Mis-Invocation Prevention

Review each skill's description.

Good descriptions:

  • name specific trigger words;
  • define a narrow scope;
  • explain boundaries.

Risky descriptions:

  • "use for all tasks";
  • "always run";
  • "do everything";
  • broad wording that overlaps with many workflows.

If a skill is useful but too broad, narrow its description. If two skills overlap, prefer one and disable the weaker one.

Clone this wiki locally