| name | find-skills |
| version | 1.0.8 |
| description | MANDATORY: For requests asking whether a skill or specialized capability exists, load this skill and run its catalog workflow before answering. This includes elliptical follow-ups such as 'find something that does' when the preceding turn names the task. Do not answer from general capabilities, search workspace filenames, or use generic web search. |
| comis | {"requires":{"bins":["git"]}} |
Find Skills
Discover and install skills from the open agent skills ecosystem into Comis.
All script paths below are relative to this skill's directory. Resolve them against the directory containing the manifest file shown in <location>.
Invoke the resolved script by its absolute path while keeping the tool working directory inside the execution workspace. Never set cwd to the skill directory; it is outside workspace bounds. In command examples below, replace each relative scripts/... path with its resolved absolute path.
Workflow
Step 1: Distinguish installed state from catalog discovery
An installed-state request refers to the agent's current list or asks whether something is already
"installed", "available", or "in there". For an installed-state request, call skills_manage with
action: "list" first and answer only from that result. Do not run the public catalog search unless
the user separately asks to find an alternative.
A catalog result never proves that a skill is installed. Exit code 0 from npx skills find proves
only that the search completed and returned candidates. Never count a catalog candidate as installed,
describe it as newly installed, or call the current registry list stale.
Step 2: Understand what they need
Identify the domain (e.g., React, testing, deployment), the specific task (e.g., writing tests, reviewing PRs), and whether a skill likely exists for it.
Step 3: Search for skills
For an existing-skill discovery request, you must run npx skills find <query> first through exec
in the execution workspace. Use the non-interactive form:
Call exec directly for this catalog command. Do not call the find file tool: it searches
workspace filenames and cannot search the skills catalog. For an elliptical follow-up, derive
<query> from the concrete task named in the preceding user request; never search for the literal
follow-up wording.
npx --yes skills find <query>
Examples:
- User asks "how do I make my React app faster?" --
npx skills find react performance
- User asks "can you help with PR reviews?" --
npx skills find pr review
- User asks "I need to create a changelog" --
npx skills find changelog
Do not substitute generic web search while the native catalog command is available. If the command
is missing or fails, report that exact limitation and offer direct help; never imply that a catalog
skill was found.
Step 4: Present options
Present the strongest verified fit as the clear recommendation, including its
owner/repo@skill-name identifier. Mention alternatives only when they materially differ. Do not
claim details the catalog output did not establish.
The same-turn response after a successful catalog search must name one exact owner/repo@skill-name identifier.
Saying only that tools exist is incomplete and leaves a later
"install it" request without a verified target.
Step 5: Install
Never copy a skill into ~/.comis/skills/ and never use npx skills add; those paths bypass Comis's
scoped registry, content scan, and approval gate.
When the user asks to install a catalog result:
-
Resolve its exact GitHub directory URL with the bundled resolver:
bash scripts/resolve-skill-url.sh <owner/repo@skill-name>
-
Call skills_manage with action: "import", that URL, and scope: "local". Local scope installs
into the calling agent's workspace. Use scope: "shared" only when the user explicitly asks for
a shared install and the calling agent is authorized.
-
Let the normal approval gate complete; do not claim installation while approval is pending or
denied.
-
Call skills_manage with action: "list" and confirm the returned entry. Report the exact
returned location as installation ground truth.
The skill watcher makes a successfully listed import available without a daemon restart.
Common Skill Categories
| Category | Example Queries |
|---|
| Web Development | react, nextjs, typescript, css, tailwind |
| Testing | testing, jest, playwright, e2e |
| DevOps | deploy, docker, kubernetes, ci-cd |
| Documentation | docs, readme, changelog, api-docs |
| Code Quality | review, lint, refactor, best-practices |
| Design | ui, ux, design-system, accessibility |
| Productivity | workflow, automation, git |
When No Skills Are Found
- Acknowledge that no existing skill was found
- Offer to help with the task directly using general capabilities
- Suggest the user could create their own skill using the skill-creator skill
