skills-discovery-curation

To inventory and curate skills across repositories, this skill discovers available and installed Codex skills, ranks candidates with arbiter-based checks, and builds a prioritized, auditable portfolio. It requires a root SKILL.md file with a name and description to function.

Arbiter-based admission for skill governance is a workflow that evaluates discovered skill candidates using evidence checks before allowing them into your portfolio. This process ensures safe, auditable curation runs for personal lockdown mode.

Yes, you can run a one-time skills audit without recurring workflows. The curation process applies to both one-time audits and recurring curation runs, inventorying skills across repositories and ranking candidates based on evidence checks.

Yes, you need a root SKILL.md file containing a name and description to use the skills discovery workflow. Optional references, scripts, and assets directories, along with dependency and component metadata, can also be included for deeper curation.

The best way to prioritize Codex skill candidates safely is using the admission workflow with arbiter-based checks and personal-lockdown mode. This approach ranks candidates systematically while maintaining an auditable governance trail.

Manual skill discovery and curation is time-consuming and error-prone, making it difficult for teams to accurately inventory skills, compare candidates, and admit safe ones without automated governance workflows and evidence checks.