finding-google-skills
Helps an agent choose and set up Google products for a stack decision (where to run a service, a database, storage, auth, analytics, AI serving) by loading Google's skill catalog on demand.
- Kind
- Skill
- Works with
- Any agent
- Source
- Google skills (Google Cloud and more) @ 92776fbf3875
- Path
- skills/developers/finding-google-skills/SKILL.md
- Jobs
- Planning
Credit
- Made by
- Original
- github.com/google/skills/blob/92776fbf3875a5ee7424124e398956a…
- License
- Apache-2.0
Listed by Skill Manifest; not made by us.
InstallInstall it with npx.
npx skills add google/skills
Install factsScanned 2 Nov 2026
- Adds
- .claude/skills/finding-google-skills/ (the skill folder)
- Runs scripts
- Yes
- shell block in the text
- Uses the network
- Yes
- curl / wget
- Needs secrets
- None found
- Source revision
- 92776fbf3875
- Licence
- Apache-2.0
- Last activity
- 1 Nov 2026
- Review
- Reviewed
Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.
- Only the main file is read; other files in the folder are not scanned
# 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`.
…