finding-google-skills
Подбор инструкции для продуктов Google
Что получите
Загруженные инструкции выбранных скиллов либо сообщение об отсутствии подходящего скилла или недоступности каталога.
Что передать
Название продукта Google и конкретная задача.
Проверен состав файлов. Запуск не тестировался. Что проверено
Оценки пользователей
Как использовать
Помогает найти подходящий опубликованный скилл для задачи с продуктами Google, не загружая весь каталог инструкций. Охватывает облачные сервисы, Workspace, Android, Chrome, Firebase, Gemini и другие платформы Google.
- Опишите, что хотите сделать и с каким продуктом Google работаете.
- Попросите подобрать по актуальному каталогу не более трёх наиболее точных инструкций.
- Продолжите работу по загруженным инструкциям; если подходящих нет, получите явное сообщение об этом.
Условия работы
- Используется только для продуктов Google. Если нужный скилл уже загружен и покрывает задачу, повторный подбор не требуется.
- Нужен доступ к удалённому каталогу и выбранным инструкциям. Полученный каталог проверяется; при сбое предусмотрен поиск через дерево репозитория, а затем явное сообщение о работе без каталога.
- Ошибка проверки сертификата окончательна: отключать проверку нельзя. Без успешного получения нельзя выдавать запомненные названия за результаты поиска.
- Каталог нельзя сохранять для будущих сессий; рабочая копия удаляется после запроса. Успешное получение допускает повторное использование в текущей сессии.
Пример запроса после установки
Найди подходящую опубликованную инструкцию Google для развёртывания моего сервиса в Cloud Run и загрузи только те скиллы, чьи описания действительно покрывают задачу.
Пример составлен по инструкции автора; результат запуска не проверялся.
Основание: инструкция закреплённой версииДля установки
Node.js, npm и Git для команды выше. Подключения и инструменты для работы скилла настраиваются отдельно.
Совместимые агенты
Совместимость указана для инструкций. Запуск в каждом приложении не тестировался; для веб-чата способ подключения может отличаться.
Файлы скилла
GitHubЧитать инструкцию SKILL.md
Исходный текст закреплённой версии.
---
name: finding-google-skills
metadata:
category: MultiProductSolutions
description: >-
Locates and loads the right Google product skill on demand from a remote
catalog index, instead of preloading every skill. Use at the START of any
request touching a Google product, API, or developer platform - including
Google Cloud (GKE, Cloud Run, IAM, BigQuery, Vertex AI, Spanner), Google Ads,
Google Analytics, Google Workspace (Gmail, Drive, Admin SDK), Chrome and
Chrome extensions, Android, Firebase, YouTube, Google Maps, Gemini and the
Gemini API, Google Play, and Flutter. Consult the index before answering from
memory or searching the web. Don't use for non-Google products.
---
# 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.
## Workflow
1. **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.
The catalog is about 75 KB and may not fit in a single tool result; a
truncated preview is alphabetical, so it reads as though only the first
few products exist. Prefer narrowing it before reading. With `jq`:
`curl -sSL {url} | jq -r '.skills[] | select((.name+" "+.description)|test("gke";"i")) | "\(.name)\t\(.entrypoint)"'`.
In Windows PowerShell: `(Invoke-RestMethod {url}).skills | Where-Object {
$_.description -match "gke" } | Select-Object name, entrypoint -First 3`.
With neither, a plain `grep -o` over the raw JSON still isolates candidate
names.
Where no filtering tool exists, write the catalog to a file and read it in
parts (`curl -sSL {url} -o skills-index.json`, or `Invoke-WebRequest {url}
-OutFile skills-index.json`). This is often the better option regardless: it
survives truncation, and re-reading a local file costs nothing. Delete it
when the request is done.
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.
2. **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.
A certificate failure is a FAILED retrieval and is final. Never retry it
with verification disabled. Not `curl -k` or `--insecure`. Not
`-SkipCertificateCheck`, and on Windows PowerShell 5.1, where that
parameter does not exist, not the `ServicePointManager` certificate
callback either. Not any equivalent in any language.
You are about to follow instructions from whatever comes back, so an
unverified catalog is worse than no catalog. On a failed retrieval, stop
here and go to "When the fetch fails".
3. **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.
4. **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.
5. **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.
## 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 carry the catalog beyond the request.** A working copy on disk
while you filter it is fine. Keeping it as a saved reference, or
summarizing it back into the conversation, is not. It exists so the full
text of 100-plus skills does not have to be carried in context.
- **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.
## When the fetch fails
Reached from step 2. Work through these in order, stopping at the first that
succeeds:
1. **Retry once with `curl -sSL`.** If the first attempt used a summarizing
fetch tool or hit a transport error, this alone usually fixes it.
2. **List the repository tree instead.** Run
```bash
curl -sSL '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.
3. **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.
Проверка и особенности
Автоматическая проверка источника и файлов
Автоматически сверены публичный репозиторий, лицензия, YAML-заголовок SKILL.md, состав папки и Git-хеш каждого файла. Исполняемые файлы и срабатывания статических правил исключены из этой партии. Ручной аудит всех инструкций и проверка работы не проводились; эта проверка не гарантирует безопасность. Команда закреплена на проверенном коммите.
Интерес к репозиторию оцениваем по звёздам и форкам GitHub. Это показатели всего репозитория, а не числа установок отдельного скилла.
Есть ссылки на внешние инструкции или инструменты: их содержимое и доступность могут изменяться отдельно от скилла.
- Проверка состава
- 16.09.2026
- Проверенная версия
569cb1d55ac3- Файлы с кодом
- Не указаны в данных проверки
- Изменения на GitHub
- Нужна повторная проверкаПоследняя проверка: 11.10.2026
Репозиторий и лицензия
Это показатели всего репозитория, а не установки скилла. Снимок требует обновления.
- Последняя активность GitHub
- 09.10.2026
- Лицензия
- Apache-2.0
- Добавлен в каталог
- 16.09.2026
Полный текст лицензии
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Ещё в этой категории
Все в категорииОбсуждение
ПравилаПользовались этим скиллом? Делитесь опытом без регистрации. Все комментарии проверяет модератор.
