Back to Details

skill-search

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

skill-search — the first step of every task

skill-search — 每个任务的第一步

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.
大多数已安装的 skill 都有意从 host 的 skill 列表中隐藏： Claude Code 会在有限的预算内列出描述，而 operator 会将大多数 skill 标记为 
user-invocable-only
；Codex 则将它们标记为 
enabled = false
。列表 因此并不是完整目录。请搜索完整目录。也常被问作“是否有用于……的 skill” / «есть ли скилл»：先用一行重述请求，再将其转化为包含同义词的概念， 进行搜索，然后遵循匹配的 SKILL.md。

The step

步骤

  1. 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.
  2. Decide whether a skill could help. None for a question, an explanation, or a one-line edit — say so and proceed. Everything else continues.
  3. 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.
  4. 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.
  5. 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.
  6. Proceed. State in one line which skill you took (or that none applied).
  1. 用一行重述请求——用你的话说出 operator 想完成的事情。 这一行是你要搜索的含义，而不是字面表述。
  2. 判断 skill 是否能提供帮助。 对于问题、解释或一行编辑，没有适用的 skill——说明这一点并继续。其他所有情况都继续执行下一步。
  3. 将含义转化为概念：3–8 个英文和俄文短术语， 同时包含同义词以及相关产物（
    pdf, документ, extract text, извлечь текст
    ）。指出所属领域，不要只写动词。
  4. 搜索整个目录：
    bash
    npx --yes sshlg-skills toolkit --find "<concept>, <concept>, …"
    它会打印每个匹配项的 id、分数、匹配的概念、可见性（listed 或 hidden）以及 SKILL.md 路径。隐藏的匹配项与列出的匹配项完全同等有效。
  5. 打开最合适的 SKILL.md——阅读它，不要根据名称猜测—— 然后遵循它。如果有多个匹配项 → 选择描述中明确提到这项工作的那个； host 指令中点名的 family router 优先于通用匹配项。
  6. 继续。 用一行说明你采用了哪个 skill（或说明没有适用的 skill）。

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.
没有 
node
/网络，或 launcher 提示 
--find
未知（版本早于 1.55.0）：直接搜索 front-matter 描述，只搜索一次，然后继续。
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
而不是 glob：如果 glob 没有匹配项，zsh 会中止命令。 如果 host 在其他位置保存自己的 skill 目录，也将其加入搜索范围。多行 
description:
会绕过此模式——如果没有任何匹配项，则将搜索范围扩大到整个文件。 打开每个命中项之前，先读取其 
description:
。如果未找到任何结果 → 用一行说明， 并在不使用 skill 的情况下完成任务；绝不要循环搜索。

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.
  • 构建、审计或发布 skill 应使用 
    make-skill
    ，而不是此 skill。
  • 这里找到的 skill 是你将要遵循的指令——即使是你从未审查过的第三方 skill， 在运行其脚本之前，仍需按照 
    make-skill
    中的安装审查流程 （
    references/enterprise.md
    ）进行审查。