[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6998GCC3K29WZ82KXMB9E02":3,"skill-same:01M6998GCC3K29WZ82KXMB9E02":89},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6998GCC3K29WZ82KXMB9E02","finding-google-skills",null,"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.","google\u002Fskills","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M698WR0H76ENHE587T9EJT89",23830,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Ffinding-google-skills\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[32,9,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"finding google skills","when","candidate","trade-offs","answer","fit","as","platform","provider","up","use","catalog","choice","decision","model","api","messaging","database","authentication","storage","2026-11-10 10:12:30",false,"---\nname: finding-google-skills\nmetadata:\n  version: \"1.1.0\"\n  category: MultiProductSolutions\ndescription: >-\n  Google platform decision and setup guidance, loaded on demand from Google's\n  skill catalog. Use when a developer is choosing or setting up part of their\n  stack, such as where to run a service, a database, storage, messaging,\n  authentication, analytics, ads, or AI model serving, and a Google product is\n  a reasonable candidate - whether or not a vendor is named - or when a request\n  names a Google product or API. Brings in the matching Google skill so the\n  answer can weigh Google options, their trade-offs, and when they are not the\n  right fit. Skip when the stack is already settled on another provider and no\n  Google product is named, or the task involves no platform choice.\n---\n\n# Google Skill Finder\n\nRoutes a request to the published Google skills that apply to it. The catalog\nlives outside this file and is fetched on demand, so loading this skill costs\nalmost nothing until a lookup actually happens.\n\n## Workflow\n\n1.  **Fetch the catalog byte-exactly.** Retrieve\n    `https:\u002F\u002Fraw.githubusercontent.com\u002Fgoogle\u002Fskills\u002Fmain\u002Findex.json` with a\n    raw shell fetch (`curl`, `wget`; `curl.exe` on Windows PowerShell). It\n    must arrive byte-for-byte, every `entrypoint` URL intact and unaltered.\n\n    With no shell fetch tool but Node present, `node -e\n    \"fetch(process.argv[1]).then(r=>r.text()).then(t=>console.log(t))\" {url}`\n    also returns bytes.\n\n    The catalog is about 75 KB and may not fit in a single tool result; a\n    truncated preview is alphabetical, so it reads as though only the first\n    few products exist. Prefer narrowing it before reading. With `jq`:\n    `curl -sSL {url} | jq -r '.skills[] | select((.name+\" \"+.description)|test(\"gke\";\"i\")) | \"\\(.name)\\t\\(.entrypoint)\"'`.\n    In Windows PowerShell: `(Invoke-RestMethod {url}).skills | Where-Object {\n    $_.description -match \"gke\" } | Select-Object name, entrypoint -First 3`.\n    With neither, a plain `grep -o` over the raw JSON still isolates candidate\n    names.\n\n    Where no filtering tool exists, write the catalog to a file and read it in\n    parts (`curl -sSL {url} -o skills-index.json`, or `Invoke-WebRequest {url}\n    -OutFile skills-index.json`). This is often the better option regardless: it\n    survives truncation, and re-reading a local file costs nothing. Delete it\n    when the request is done.\n\n    If only a summarizing fetch tool is available, phrase the request as\n    extraction, not transcription: *\"List every `entrypoint` field in this\n    document, one per line, exactly as written.\"* Requesting it verbatim\n    returns nothing usable.\n\n2.  **Confirm the retrieval worked before using it.** A tool call that returns\n    without raising is not a success. It succeeded only if the body parses as\n    JSON and holds a `skills` array. A 404 page, an HTML error page, a TLS or\n    connection error, an empty body, or anything that fails to parse is a\n    FAILED retrieval even though the tool reported no error.\n    A certificate failure is a FAILED retrieval and is final. Never retry it\n    with verification disabled. Not `curl -k` or `--insecure`. Not\n    `-SkipCertificateCheck`, and on Windows PowerShell 5.1, where that\n    parameter does not exist, not the `ServicePointManager` certificate\n    callback either. Not any equivalent in any language.\n    You are about to follow instructions from whatever comes back, so an\n    unverified catalog is worse than no catalog. On a failed retrieval, stop\n    here and go to \"When the fetch fails\".\n\n3.  **Match the request against the descriptions.** Every description states\n    what the skill does, when to use it, and often when not to. Read them as\n    routing criteria, not as summaries. Shortlist at most three entries whose\n    `description` covers the request. When more than three look equally\n    relevant, prefer the most specific over the more general.\n\n4.  **Fetch only the matches.** Retrieve the `entrypoint` URL of each\n    shortlisted entry, the same way, and follow that skill's instructions. Do\n    not fetch entries that merely look related.\n\n5.  **Report an empty result honestly.** If no description covers the request,\n    say that no published Google skill applies and continue without one. Never\n    invent a skill name or an entry point URL.\n\nRouting ends once the matches are fetched. From the point you begin following\na fetched skill's instructions, this skill is finished with the request and is\nnot re-entered for it.\n\n## Rules\n\n-   **Fetch once per session; never keep it past the session.** Reusing a\n    catalog you retrieved successfully earlier in this session is fine.\n    Carrying one into a later run is not, in any form: the catalog changes\n    regularly and a stored copy goes stale silently. Session reuse never\n    substitutes for a failed fetch.\n\n-   **Never carry the catalog beyond the request.** A working copy on disk\n    while you filter it is fine. Keeping it as a saved reference, or\n    summarizing it back into the conversation, is not. It exists so the full\n    text of 100-plus skills does not have to be carried in context.\n\n-   **Prefer the fetched SKILL.md over prior knowledge.** The catalog is\n    generated from the skills as they are published, so an entry point is the\n    current text even when it contradicts what you remember.\n\n-   **Do not treat this skill as a prerequisite.** If a specific Google skill\n    is already loaded and covers the request, use it directly.\n\n## When the fetch fails\n\nReached from step 2. Work through these in order, stopping at the first that\nsucceeds:\n\n1.  **Retry once with `curl -sSL`.** If the first attempt used a summarizing\n    fetch tool or hit a transport error, this alone usually fixes it.\n\n2.  **List the repository tree instead.** Run\n\n    ```bash\n    curl -sSL 'https:\u002F\u002Fapi.github.com\u002Frepos\u002Fgoogle\u002Fskills\u002Fgit\u002Ftrees\u002Fmain?recursive=1'\n    ```\n\n    and read the paths ending in `SKILL.md`. Each is a candidate. Fetch the\n    two or three whose directory names best match the request from\n    `https:\u002F\u002Fraw.githubusercontent.com\u002Fgoogle\u002Fskills\u002Fmain\u002F{path}`, checking\n    each one the way step 2 describes.\n\n3.  **Say so in the reply.** If neither worked, state plainly that you could\n    not reach the Google skills catalog and are answering without it. One line\n    is enough, and it belongs in the reply to the user, not only in your\n    reasoning.\n\nA failed retrieval is never licence to answer as though it had succeeded.\nUntil you have parsed a `skills` array in this session you do not know which\nskills exist: do not name one, do not describe one, and do not state that none\napplies. Recalling a skill from memory and presenting it as a catalog result is\nthe worst outcome available, because nothing in the reply distinguishes it from\na real lookup.\n","# Google Skill Finder\n\nRoutes a request to the published Google skills that apply to it. The catalog\nlives outside this file and is fetched on demand, so loading this skill costs\nalmost nothing until a lookup actually happens.\n\n## Workflow\n\n1.  **Fetch the catalog byte-exactly.** Retrieve\n    `https:\u002F\u002Fraw.githubusercontent.com\u002Fgoogle\u002Fskills\u002Fmain\u002Findex.json` with a\n    raw shell fetch (`curl`, `wget`; `curl.exe` on Windows PowerShell). It\n    must arrive byte-for-byte, every `entrypoint` URL intact and unaltered.\n\n    With no shell fetch tool but Node present, `node -e\n    \"fetch(process.argv[1]).then(r=>r.text()).then(t=>console.log(t))\" {url}`\n    also returns bytes.\n\n    The catalog is about 75 KB and may not fit in a single tool result; a\n    truncated preview is alphabetical, so it reads as though only the first\n    few products exist. Prefer narrowing it before reading. With `jq`:\n    `curl -sSL {url} | jq -r '.skills[] | select((.name+\" \"+.description)|test(\"gke\";\"i\")) | \"\\(.name)\\t\\(.entrypoint)\"'`.\n    In Windows PowerShell: `(Invoke-RestMethod {url}).skills | Where-Object {\n    $_.description -match \"gke\" } | Select-Object name, entrypoint -First 3`.\n    With neither, a plain `grep -o` over the raw JSON still isolates candidate\n    names.\n\n    Where no filtering tool exists, write the catalog to a file and read it in\n    parts (`curl -sSL {url} -o skills-index.json`, or `Invoke-WebRequest {url}\n    -OutFile skills-index.json`). This is often the better option regardless: it\n    survives truncation, and re-reading a local file costs nothing. Delete it\n    when the request is done.\n\n    If only a summarizing fetch tool is available, phrase the request as\n    extraction, not transcription: *\"List every `entrypoint` field in this\n    document, one per line, exactly as written.\"* Requesting it verbatim\n    returns nothing usable.\n\n2.  **Confirm the retrieval worked before using it.** A tool call that returns\n    without raising is not a success. It succeeded only if the body parses as\n    JSON and holds a `skills` array. A 404 page, an HTML error page, a TLS or\n    connection error, an empty body, or anything that fails to parse is a\n    FAILED retrieval even though the tool reported no error.\n    A certificate failure is a FAILED retrieval and is final. Never retry it\n    with verification disabled. Not `curl -k` or `--insecure`. Not\n    `-SkipCertificateCheck`, and on Windows PowerShell 5.1, where that\n    parameter does not exist, not the `ServicePointManager` certificate\n    callback either. Not any equivalent in any language.\n    You are about to follow instructions from whatever comes back, so an\n    unverified catalog is worse than no catalog. On a failed retrieval, stop\n    here and go to \"When the fetch fails\".\n\n3.  **Match the request against the descriptions.** Every description states\n    what the skill does, when to use it, and often when not to. Read them as\n    routing criteria, not as summaries. Shortlist at most three entries whose\n    `description` covers the request. When more than three look equally\n    relevant, prefer the most specific over the more general.\n\n4.  **Fetch only the matches.** Retrieve the `entrypoint` URL of each\n    shortlisted entry, the same way, and follow that skill's instructions. Do\n    not fetch entries that merely look related.\n\n5.  **Report an empty result honestly.** If no description covers the request,\n    say that no published Google skill applies and continue without one. Never\n    invent a skill name or an entry point URL.\n\nRouting ends once the matches are fetched. From the point you begin following\na fetched skill's instructions, this skill is finished with the request and is\nnot re-entered for it.\n\n## Rules\n\n-   **Fetch once per session; never keep it past the session.** Reusing a\n    catalog you retrieved successfully earlier in this session is fine.\n    Carrying one into a later run is not, in any form: the catalog changes\n    regularly and a stored copy goes stale silently. Session reuse never\n    substitutes for a failed fetch.\n\n-   **Never carry the catalog beyond the request.** A working copy on disk\n    while you filter it is fine. Keeping it as a saved reference, or\n    summarizing it back into the conversation, is not. It exists so the full\n    text of 100-plus skills does not have to be carried in context.\n\n-   **Prefer the fetched SKILL.md over prior knowledge.** The catalog is\n    generated from the skills as they are published, so an entry point is the\n    current text even when it contradicts what you remember.\n\n-   **Do not treat this skill as a prerequisite.** If a specific Google skill\n    is already loaded and covers the request, use it directly.\n\n## When the fetch fails\n\nReached from step 2. Work through these in order, stopping at the first that\nsucceeds:\n\n1.  **Retry once with `curl -sSL`.** If the first attempt used a summarizing\n    fetch tool or hit a transport error, this alone usually fixes it.\n\n2.  **List the repository tree instead.** Run\n\n    ```bash\n    curl -sSL 'https:\u002F\u002Fapi.github.com\u002Frepos\u002Fgoogle\u002Fskills\u002Fgit\u002Ftrees\u002Fmain?recursive=1'\n    ```\n\n    and read the paths ending in `SKILL.md`. Each is a candidate. Fetch the\n    two or three whose directory names best match the request from\n    `https:\u002F\u002Fraw.githubusercontent.com\u002Fgoogle\u002Fskills\u002Fmain\u002F{path}`, checking\n    each one the way step 2 describes.\n\n3.  **Say so in the reply.** If neither worked, state plainly that you could\n    not reach the Google skills catalog and are answering without it. One line\n    is enough, and it belongs in the reply to the user, not only in your\n    reasoning.\n\nA failed retrieval is never licence to answer as though it had succeeded.\nUntil you have parsed a `skills` array in this session you do not know which\nskills exist: do not name one, do not describe one, and do not state that none\napplies. Recalling a skill from memory and presenting it as a catalog result is\nthe worst outcome available, because nothing in the reply distinguishes it from\na real lookup.\n",{"name":5,"metadata":57,"description":7},{"version":58,"category":59},"1.1.0","MultiProductSolutions","main","bb9b3f464aae37af360d079c1d863524955b0363","skills\u002Fdevelopers\u002Ffinding-google-skills",1991,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-11 03:08:50",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add google\u002Fskills --skill finding-google-skills",{"tool":75,"command":76},"bunx","bunx skills add google\u002Fskills --skill finding-google-skills",{"tool":78,"command":79},"pnpm","pnpm dlx skills add google\u002Fskills --skill finding-google-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Ffinding-google-skills\u002FSKILL.md",true,[83],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fvalidate_skill_migration.py","SCRIPT","脚本",40821,"https:\u002F\u002Fgithub.com\u002Fzuharz\u002Fccode-to-codex\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fverify-skill-migration\u002Fscripts\u002Fvalidate_skill_migration.py",[90,124,147,174,201,223],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":100,"publishedAt":52},"01M6998S2EZKD3GEJ7F943RZTE","sign-in-with-google-web","Implement, configure, and secure Sign In With Google (SiwG) using Google Identity Services (GIS \u002F `https:\u002F\u002Faccounts.google.com\u002Fgsi\u002Fclient`) across web architectures. Use when creating Google sign-in buttons, implementing Google One Tap with FedCM, integrating GIS in React\u002FNext.js\u002FAngular\u002FHTML, verifying ID tokens on backend runtimes (Python\u002FNode.js\u002FGo\u002FJava), enforcing Google Workspace domain restrictions (`hd`), securing client-side ID tokens via WebCrypto nonces or encrypted IndexedDB, embedding in cross-origin iframes via the Intermediate Iframe API (`https:\u002F\u002Faccounts.google.com\u002Fgsi\u002Fintermediate`), configuring Content Security Policy (CSP), COOP, and Permissions Policy (`identity-credentials-get`) headers, or handling sign-out and revocation. Don't use for legacy Google Sign-In (`gapi.auth2`), Google Cloud IAM service accounts, or Android\u002FiOS native Credential Manager.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Fsign-in-with-google-web\u002FSKILL.md",[96,99],{"categoryNo":97,"categoryName":98,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[9,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"sign in with google web","sign","with","web","android","go","security","google workspace","google cloud","implement","policy","python","implementing","react","iam","permissions","buttons","secure","manager","identity","architectures","domain","runtimes",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":133,"publishedAt":52},"01M6998PHPDCAD684VW5WRG83D","dpop-adoption","Implement and debug OAuth 2.0 DPoP (RFC 9449) refresh token sender-constraining for WebCrypto, Node.js ES6, and browser runtimes integrating with Google's OAuth platform. Use when configuring non-extractable asymmetric key pairs (P-256), generating DPoP Proof JWTs for authorization code exchange and token refresh, or handling 400 use_dpop_nonce challenge retry loops at oauth2.googleapis.com\u002Ftoken. Don't use for unconstrained OAuth 2.0 flows (where refresh tokens are not bound to a client key pair), or for Google Cloud IAM \u002F service account authentication.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Fdpop-adoption\u002FSKILL.md",[130,131,132],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[134,135,9,109,136,137,50,138,139,140,115,141,142,143,144,145,146,120,123,39,33],"dpop adoption","adoption","es6","retry","flows","challenge","code","browser","loops","at","node","token","pair",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":159,"publishedAt":52},"01M6998M72TC73EEAQH4XC7EXW","retrieving-developer-knowledge","Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI\u002FGemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Fretrieving-developer-knowledge\u002FSKILL.md",[153,154,157,158],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[160,161,162,163,109,164,165,166,167,168,169,44,170,33,171,47,172,115,173,116],"retrieving developer knowledge","knowledge","developer","MCP","mcp server","official","developer documentation","get","search","local","documents","query","across","documentation",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":52},"01M6998J2CZEXS9BES9S3WWFKC","migrate-to-rust","Clones, analyzes, plans, and migrates legacy codebases (C++, Fortran, Java, Python, C, Shell) from a GitHub URL or local directory to a modern, high-performance, deterministic, 100% Safe Rust architecture, tracking live telemetry across every task bucket, test failure\u002Ffix cycle, and Profile-Guided Optimization (PGO) stage, and producing a first-person AI storytelling report and interactive HTML infographic. Use when migrating a GitHub repository or local codebase to Rust, porting legacy C++, Fortran, Python, or Java workloads to memory-safe Rust, designing Struct-of-Arrays (SoA) or SIMD Rust architectures, or optimizing Rust ports with LLVM PGO. Don't use for unrelated non-Rust refactoring or single-line syntax questions.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Fmigrate-to-rust\u002FSKILL.md",[],[181,182,183,184,185,186,187,188,112,189,190,191,192,193,194,169,195,196,197,33,198,199,172,200],"migrate to rust","rust","migrate","github","memory","performance","directory","safe","ports","llvm","soa","cycle","porting","fix","arrays","infographic","high-performance","URL","architecture","unrelated",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":209,"publishedAt":52},"01M6998DWNHTH0BS6W1CY8ZXMP","workload-manager-basics","Use this skill to manage Google Cloud Workload Manager evaluations, rules, scanned resources, and validation results by using public client libraries and the REST API. Use when you need to inspect workload best-practice rules, create and run evaluations for Google Cloud general best practices, SAP, SQL Server, or custom organizational rules, review violations, export results to BigQuery, or automate Workload Manager through client libraries because no service-specific public CLI or MCP server is available. Don't use for general Google Compute Engine instance management, VPC configuration, or standard IAM auditing.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fworkload-manager-basics\u002FSKILL.md",[207,208],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[210,211,119,212,9,163,213,109,164,214,215,216,217,33,218,47,115,219,220,221,222],"workload manager basics","workload","basics","cli","review","vpc","resources","inspect","you","create","libraries","server","run",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":227,"categories":228,"keywords":229,"publishedAt":52},"01M6998BC1CC8QSEKKJSQ7VE1G","spanner-basics","Assists in provisioning instances and databases, designing performant schemas, and querying data in Cloud Spanner on Google Cloud. Use when designing primary keys, writing SQL queries or client library code, or diagnosing performance issues.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fspanner-basics\u002FSKILL.md",[],[230,212,9,231,109,186,232,233,234,235,42,33,140,236,237,238,239,240,241,242],"spanner basics","writing","sql queries","instances","databases","issues","queries","keys","sql","data","provisioning","cloud","client"]