finding-google-skills

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Google Skill Finder

Routes a request to the published Google skills that apply to it. The catalog lives outside this file and is fetched on demand, so loading this skill costs almost nothing until a lookup actually happens.

将请求路由至适用的已发布Google Skill。目录存储在本文件之外，按需获取，因此在实际执行查找前，加载此Skill几乎不会产生任何开销。

Workflow

工作流程

Fetch the catalog byte-exactly. Retrieve
```
https://raw.githubusercontent.com/google/skills/main/index.json
```
with a raw shell fetch (
```
curl
```
,
```
wget
```
;
```
curl.exe
```
on Windows PowerShell). It must arrive byte-for-byte, every
```
entrypoint
```
URL intact and unaltered.
With no shell fetch tool but Node present,
```
node -e "fetch(process.argv[1]).then(r=>r.text()).then(t=>console.log(t))" {url}
```
also returns bytes.
If only a summarizing fetch tool is available, phrase the request as extraction, not transcription: "List every
entrypoint
field in this document, one per line, exactly as written." Requesting it verbatim returns nothing usable.
Confirm the retrieval worked before using it. A tool call that returns without raising is not a success. It succeeded only if the body parses as JSON and holds a
```
skills
```
array. A 404 page, an HTML error page, a TLS or connection error, an empty body, or anything that fails to parse is a FAILED retrieval even though the tool reported no error. On a failed retrieval, stop here and go to "When the fetch fails".
Match the request against the descriptions. Every description states what the skill does, when to use it, and often when not to. Read them as routing criteria, not as summaries. Shortlist at most three entries whose
```
description
```
covers the request. When more than three look equally relevant, prefer the most specific over the more general.
Fetch only the matches. Retrieve the
```
entrypoint
```
URL of each shortlisted entry, the same way, and follow that skill's instructions. Do not fetch entries that merely look related.
Report an empty result honestly. If no description covers the request, say that no published Google skill applies and continue without one. Never invent a skill name or an entry point URL.

Routing ends once the matches are fetched. From the point you begin following a fetched skill's instructions, this skill is finished with the request and is not re-entered for it.

精确获取目录的字节内容：通过原生Shell获取工具（
```
curl
```
、
```
wget
```
；Windows PowerShell中使用
```
curl.exe
```
）检索
```
https://raw.githubusercontent.com/google/skills/main/index.json
```
。必须保证内容字节级完整，每个
```
entrypoint
```
URL保持原样且未被修改。
若没有Shell获取工具但已安装Node.js，可使用命令
```
node -e "fetch(process.argv[1]).then(r=>r.text()).then(t=>console.log(t))" {url}
```
，同样能返回字节内容。
若仅能使用摘要型获取工具，请将请求表述为提取而非转录："列出此文档中的每个
entrypoint
字段，每行一个，严格保持原文格式。" 请求逐字转录将无法得到可用内容。
在使用前确认检索成功：工具调用未抛出异常并不代表成功。只有当返回内容可解析为JSON且包含
```
skills
```
数组时，才算成功检索。若返回404页面、HTML错误页面、TLS或连接错误、空内容或无法解析的内容，即便工具未报错，也属于检索失败。若检索失败，停止当前流程，进入「检索失败时的处理」环节。
将请求与描述进行匹配：每个描述都会说明该Skill的功能、适用场景，通常还会说明不适用场景。请将这些描述视为路由判定标准，而非简单摘要。筛选出最多3个
```
description
```
与请求匹配的条目。若超过3个条目看起来相关性相同，优先选择更具体的条目。
仅获取匹配的条目：按照相同方式检索每个入围条目的
```
entrypoint
```
URL，并遵循该Skill的指令。请勿获取仅看似相关的条目。
如实报告空结果：若没有任何描述匹配请求，请告知用户没有适用的已发布Google Skill，然后继续处理（不使用Skill）。切勿编造Skill名称或入口点URL。

获取到匹配条目后，路由流程结束。从开始遵循已获取Skill的指令起，本Skill将不再参与该请求的后续处理。

Rules

规则

Fetch once per session; never keep it past the session. Reusing a catalog you retrieved successfully earlier in this session is fine. Carrying one into a later run is not, in any form: the catalog changes regularly and a stored copy goes stale silently. Session reuse never substitutes for a failed fetch.
Never copy the catalog into a file, a reference, or a reply. It exists so that the full text of 100-plus skills does not have to be carried in context. Summarizing it back into the conversation defeats that.
Prefer the fetched SKILL.md over prior knowledge. The catalog is generated from the skills as they are published, so an entry point is the current text even when it contradicts what you remember.
Do not treat this skill as a prerequisite. If a specific Google skill is already loaded and covers the request, use it directly.

每个会话仅获取一次；会话结束后请勿保留：在本次会话中复用之前成功检索到的目录是允许的，但禁止以任何形式将目录带入后续会话——目录会定期更新，存储的副本会悄然过期。会话复用不能替代失败的检索操作。
切勿将目录复制到文件、参考资料或回复中：目录的存在意义在于避免在上下文加载100多个Skill的完整文本。将其摘要后放回对话会违背这一初衷。
优先使用获取到的SKILL.md而非已有知识：目录是根据已发布的Skill生成的，因此即使入口点的内容与你的记忆不符，它也是当前的最新文本。
请勿将本Skill视为前置条件：若已加载特定的Google Skill且该Skill适用于当前请求，请直接使用它。

When the fetch fails

检索失败时的处理

Reached from step 2. Work through these in order, stopping at the first that succeeds:

Retry once with
curl -sS
. If the first attempt used a summarizing fetch tool or hit a transport error, this alone usually fixes it.
List the repository tree instead. Run
bash
```
curl -sS https://api.github.com/repos/google/skills/git/trees/main?recursive=1
```
and read the paths ending in
```
SKILL.md
```
. Each is a candidate. Fetch the two or three whose directory names best match the request from
```
https://raw.githubusercontent.com/google/skills/main/{path}
```
, checking each one the way step 2 describes.
Say so in the reply. If neither worked, state plainly that you could not reach the Google skills catalog and are answering without it. One line is enough, and it belongs in the reply to the user, not only in your reasoning.

A failed retrieval is never licence to answer as though it had succeeded. Until you have parsed a

skills

array in this session you do not know which skills exist: do not name one, do not describe one, and do not state that none applies. Recalling a skill from memory and presenting it as a catalog result is the worst outcome available, because nothing in the reply distinguishes it from a real lookup.

从步骤2进入此环节，请按以下顺序尝试，直到首次成功为止：

使用
curl -sS
重试一次：若首次尝试使用的是摘要型获取工具或遇到传输错误，此操作通常可解决问题。
改为列出仓库目录结构：执行
bash
```
curl -sS https://api.github.com/repos/google/skills/git/trees/main?recursive=1
```
并读取以
```
SKILL.md
```
结尾的路径。每个路径都是候选条目。从
```
https://raw.githubusercontent.com/google/skills/main/{path}
```
获取2-3个目录名称与请求最匹配的条目，并按照步骤2的方式检查每个条目。
在回复中如实说明：若以上两种方式均失败，请直接告知用户无法访问Google Skill目录，将在未使用该目录的情况下回答问题。只需一句话说明即可，且需包含在给用户的回复中，而非仅在你的思考过程中。

检索失败绝不允许假装检索成功。在本次会话中解析到

skills

数组之前，你无法知晓哪些Skill存在：请勿提及任何Skill名称、描述Skill内容，也勿断言没有适用的Skill。凭记忆回忆Skill并将其作为目录检索结果呈现是最糟糕的情况，因为回复中没有任何内容能区分它与真实的检索结果。