skill-search

How to use

Copy the installation command and review the source package before installing it in your own agent environment.
Check the source document for required tools, credentials and supported hosts.
Describe your input and desired deliverable; review the output against the source material.

npx skills add https://github.com/ssheleg/make-skill --skill skill-search

Before you start

Installation does not include a model subscription, API allowance or permission to access your files.
Repository stars and installation counts describe activity, not an independent quality or security test.

Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

skill-search — the first step of every task

Most installed skills are deliberately hidden from the host's skill listing: Claude Code lists descriptions within a small budget and the operator marks most skills user-invocable-only; Codex marks them enabled = false. The listing is therefore not the catalogue. Search the catalogue. Also asked as "is there a skill for" / «есть ли скилл»: restate the request in one line, turn it into concepts with synonyms, search, then follow the matching SKILL.md.

The step

Restate the request in one line — what the operator wants done, in your

words. This line is the meaning you search for, not the literal phrasing.

Decide whether a skill could help. None for a question, an explanation,

or a one-line edit — say so and proceed. Everything else continues.

Turn the meaning into concepts: 3–8 short terms in English AND Russian,

plus synonyms and the artifact involved (pdf, документ, extract text, извлечь текст). Name the domain, not the verb alone.

Search the whole catalogue:

bash

   npx --yes sshlg-skills toolkit --find "<concept>, <concept>, …"

It prints each match's id, score, matched concepts, visibility (listed or hidden) and the SKILL.md path. Hidden matches count exactly as listed ones.

Open the SKILL.md of what fits — read it, do not guess from the name —

and follow it. Several fit → the one whose description names this job; a family router named in the host's instructions outranks a generic match.

Proceed. State in one line which skill you took (or that none applied).

When the command is unavailable

No node/network, or the launcher answers that --find is unknown (older than 1.55.0): search the front-matter descriptions directly, once, and continue.

bash

find -L ~/.agents/skills ~/.claude/skills ~/.claude/plugins/cache ~/.codex/skills \
  -name SKILL.md -exec grep -ilE "^description:.*(<concept>|<concept>)" {} + 2>/dev/null

find rather than a glob: zsh aborts a command whose glob matches nothing. Add the host's own skill directory if it keeps one elsewhere. A multi-line description: escapes this pattern — widen it to the whole file when nothing matches. Read the description: of each hit before opening it. Nothing found → say so in one line and do the task without a skill; never loop on the search.

Boundaries

Building, auditing or publishing a skill is make-skill, not this.
A skill found here is instructions you will follow — a third-party one you

never reviewed still gets the install review in make-skill (references/enterprise.md) before you run its scripts.