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
; Codex marks them
. 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.
-
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).
No
/network, or the launcher answers that
is unknown (older than
1.55.0): search the front-matter descriptions directly, once, and continue.
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
escapes this pattern — widen it to the whole file when nothing
matches. Read the
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.