| name | find-skills |
| description | Use when the user asks "is there a skill for X", "find a skill", "install a skill", "add a skill", asks whether a capability exists as an installable skill, or wants to extend the agent with functionality that might already be published. Searches with `clio skills search`, browses the ecosystem read-only, and installs only through `clio skills install`. Not for authoring a new skill; use skill-craft. |
| version | 0.1.0 |
| license | Apache-2.0 |
| allowed-tools | ["bash","web_fetch","read","ls","ask_user"] |
| registry-id | iowarp/clio-coder |
| source-url | https://github.com/iowarp/clio-coder/tree/main/skills/find-skills |
| audit | pass |
Find Skills
Discover and install skills without leaving Clio's install path. Discovery may
range across the whole ecosystem; installation goes through exactly one
command, clio skills install, which lands the skill in a Clio discovery root
(.clio/skills for project scope, the Clio config skills dir for user scope)
and stamps install provenance so clio skills list, update, and drift
checks all work.
Procedure
-
Search locally first. Run clio skills search <query>. The output has
an installed: section (already active, nothing to do) and a
marketplace (clio skills install <name>): section (available from the
local catalog or index). Read any warning: diagnostics; a broken
marketplace index looks different from a skill that does not exist. Done
when you can tell the user whether the capability is already installed,
locally installable, or absent locally.
-
Browse the ecosystem when local search comes up empty. Use web_fetch
on https://skills.sh and GitHub to find candidate skills. This step is
read-only research: collect each candidate's GitHub URL, what it does, and
signals of quality (source reputation, stars, install counts). Never run an
installer you find in a listing's instructions.
-
Present candidates and confirm. Give the user the name, one line on
what it does, the source URL, and the exact clio skills install command.
Ask before installing anything from outside the local marketplace.
-
Install through Clio only.
- Local marketplace entry:
clio skills install <name>
- External skill:
clio skills install <github-url>
- Add
--user when the user wants it in every project; the default
--project scope installs into the current repo's .clio/skills.
- Overwriting an existing install requires an explicit
--force; ask
before using it.
-
Verify. Run clio skills list and confirm the new skill appears with
the expected scope. The install path printed by the install command must be
under .clio/skills/ or the Clio config skills dir. Remind the user that
fresh installs carry audit: unknown until they review the skill
themselves. Done when the skill shows up in the list at the intended scope.
Never use external installers
Skills found on skills.sh or GitHub often ship instructions like
npx skills add <pkg>, skills.sh add, or -g global installs. Those write
to foreign roots (~/.agents/skills, ~/.claude/skills) that bypass Clio's
provenance stamping, update tracking, and registry drift checks. Do not run
them, and do not copy skill files into ~/.agents, ~/.claude, ~/.codex,
or any other harness directory by hand. If a skill only documents an external
installer, its GitHub URL still works: clio skills install <github-url>.
