Skill Management

Manage local SKILL.md files with /skill commands. Shared execution, delegation, state, hook, team, cancellation, verification, and escalation invariants live in templates/AGENTS.md; follow that contract instead of repeating it here.

<Purpose> Create, inspect, validate, update, and organize user- or project-scoped skills. Keep each skill specific, actionable, evidence-based, and useful to this codebase. </Purpose>

<Use_When>

• The user asks to list, add, edit, remove, search, inspect, sync, set up, scan, or validate skills.
• A durable, codebase-specific solution or workflow should be captured as a skill. </Use_When>

<Do_Not_Use_When>

• Use /learner to extract a skill from a conversation and /note for a short note.
• Do not use this prompt to change runtime code, catalogs, hooks, or installation logic. </Do_Not_Use_When>

Scopes and commands

Canonical roots are ${CODEX_HOME:-$HOME/.codex}/skills/ (user) and .codex/skills/ (project). A skill lives at <root>/<name>/SKILL.md.

Command	Contract
/skill list	Scan both roots, parse frontmatter, and show name, description, triggers, scope, and quality/usage (N/A when unavail…