find-skills

Browse skills.sh or search source repositories for candidates, inspect the complete bundle including SKILL.md and all scripts, then install with the pinned Skills CLI command npx skills@<reviewed-version> add from a locally reviewed checkout. Installation requires explicit user authorization of source, scope, and target agents.

The Skills CLI is the package manager for the open agent skills ecosystem, providing find, add, and update commands. Because unversioned npx execution downloads a moving package, you should inspect the CLI package first and always pin an exact reviewed version before running it.

No. Install counts, stars, and leaderboard position are weak discovery signals only. Always inspect the complete bundle for capabilities, network access, credentials handling, provenance, license, and maintenance activity before recommending or installing any skill.

Use find-skills only when the user explicitly asks for an external skill or the installed catalogue genuinely lacks the requested capability. For choosing among already-installed local skills or selecting software libraries and frameworks, use the host's installed-skill coordination or evaluate-existing-solutions instead.

A remote owner/repo@skill source is mutable and can change between review and download, so it is not a reviewed installation. Checking out the exact inspected commit locally and verifying the bundle hash guarantees the installed bytes match what was vetted.

Acknowledge that no matching skill was found, then offer to complete the task directly with general capabilities. For recurring workflows, suggest creating a custom skill using the installed skill-creator workflow or a reviewed, pinned Skills CLI init command.