# Finding Google Skills

Google platform decision and setup guidance, loaded on demand from Google's skill catalog.

- Repository: https://github.com/google/skills (21764 stars)
- Category: Data and ML
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add google/skills --skill finding-google-skills -g -a claude-code -y`
Codex: `npx skills add google/skills --skill finding-google-skills -g -a codex -y`
Cursor: `npx skills add google/skills --skill finding-google-skills -g -a cursor -y`
Gemini CLI: `npx skills add google/skills --skill finding-google-skills -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add google/skills`

## Description

Google platform decision and setup guidance, loaded on demand from Google's skill catalog. Use when a developer is choosing or setting up part of their stack, such as where to run a service, a database, storage, messaging, authentication, analytics, ads, or AI model serving, and a Google product is a reasonable candidate - whether or not a vendor is named - or when a request names a Google product or API. Brings in the matching Google skill so the answer can weigh Google options, their trade-offs, and when they are not the right fit. Skip when the stack is already settled on another provider and no Google product is named, or the task involves no platform choice.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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.

The rest: https://github.com/google/skills/blob/HEAD/plugins/cloud/google-cloud-developer/skills/finding-google-skills/SKILL.md