skill

Run the add subcommand to launch an interactive wizard that prompts for a name, description, triggers, argument hint, and scope. It validates naming conventions (lowercase, hyphens only) and generates a SKILL.md file from a template in the chosen directory.

Use the search subcommand with a query string to match against skill names, descriptions, triggers, and full markdown content across both user and project scopes. Results are ranked with name and trigger matches prioritized over content matches.

User-level skills live in ~/.codex/skills/ and apply across all projects, while project-level skills live in .codex/skills/ and are committed with the repository for team sharing. The sync subcommand copies skills between these two scopes.

No, the remove subcommand always displays the skill's name, description, and scope, then requires explicit yes/no confirmation before deleting the skill directory. Destructive operations are never performed automatically.

Good skills are non-Googleable, context-specific to actual files and errors in the codebase, actionable with precise steps, and hard-won from real debugging effort. Generic programming advice or easily searchable content should not become skills.