[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698YWA2Q0WKQT7J3BNQCH8W":3,"skill-same:01M698YWA2Q0WKQT7J3BNQCH8W":104},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M698YWA2Q0WKQT7J3BNQCH8W","alloydb-basics",null,"Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.","google\u002Fskills","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M698WR0H76ENHE587T9EJT89",24122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Falloydb-basics\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"alloydb basics","basics","when","MCP","for","with","database operations","do","instances","general","databases","use","operations","model","gcp","postgresql","database","protocol","sql","model context protocol","2026-11-10 10:12:30",false,"---\nname: alloydb-basics\nmetadata:\n  version: \"1.0.1\"\n  category: Databases\ndescription: >-\n  Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and\n  integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations.\n  Use when creating, configuring, or administering AlloyDB databases.\n  Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.\n---\n\n# AlloyDB Basics\n\nAlloyDB for PostgreSQL is a managed, PostgreSQL-compatible database service\ndesigned for enterprise-grade performance and availability. It utilizes a\ndisaggregated compute and storage architecture to scale resources independently.\nIt also provides AlloyDB AI, a collection of features that includes AI-powered\nsearch (vector, hybrid search, and AI functions), natural language capabilities,\nconversational analytics, and inference features like forecasting and model\nendpoint management to help developers build AI apps faster.\n\n## Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read [Usage Attribution](references\u002Fattribution.md). For commands executed\ndirectly in the terminal (never in generated scripts, Terraform, or user code),\nprefix `gcloud` with\n`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION=\"agent-skills\u002F1.0 (skill:alloydb-basics)\"`\nand append `agent-skills\u002F1.0 (skill:alloydb-basics)` to `User-Agent` headers.\n\n## Quick Start\n\nBefore you begin, ensure you have the [Google Cloud SDK installed](https:\u002F\u002Fcloud.google.com\u002Fsdk\u002Fdocs\u002Finstall) and authenticated (`gcloud auth login`).\n\n1.  **Enable the AlloyDB API:**\n\n    ```bash\n    gcloud services enable alloydb.googleapis.com --quiet\n    ```\n\n2.  **Create a Cluster:**\n\n    ```bash\n    gcloud alloydb clusters create my-cluster --region=us-central1 \\\n        --password=my-password --network=my-vpc --quiet\n    ```\n\n    *For production environments, always use IAM database authentication instead\n    of passwords. If configuration constraint requires passwords, store them\n    securely using Secret Manager.*\n\n3.  **Create a Primary Instance:**\n\n    ```bash\n    gcloud alloydb instances create my-primary --cluster=my-cluster \\\n        --region=us-central1 --instance-type=PRIMARY --cpu-count=2 --quiet\n    ```\n\n## Reference Directory\n\nRead these supplementary files when specific context or detailed steps are\nrequired for a task:\n\n-   To understand architecture, regional availability, connectivity (Private IP,\n    Public IP, PSA, PSC), backups, point-in-time recovery, scaling (vertical and\n    horizontal), or Quota management: read\n    [Core Concepts](references\u002Fcore-concepts.md).\n-   To manage clusters, instances, scaling, or backups via the CLI: read\n    [CLI Usage](references\u002Fcli-usage.md).\n-   To configure AlloyDB remote MCP tools: read\n    [MCP Usage](references\u002Fmcp-usage.md).\n-   To deploy AlloyDB using Terraform or Kubernetes Config Connector (KCC): read\n    [Infrastructure as Code](references\u002Fiac-usage.md).\n-   To configure IAM roles, service usage roles, service agents, database\n    users\u002Fprivileges, or network security (public IP authorization, Auth Proxy\n    sidecar configuration): read [IAM & Security](references\u002Fiam-security.md).\n\n*If you need product information not found in these references, use the\n`developer_knowledge:search_documents` tool (see [Developer Knowledge MCP setup](https:\u002F\u002Fdevelopers.google.com\u002Fknowledge\u002Fmcp) for installation instructions).*\n\n## Directives for Agents\n\nAgents MUST adhere to the following directives when answering queries related to\nAlloyDB:\n\n-   **Provide Multiple Methods:** When explaining how to perform administrative\n    tasks (like backups, scaling, or database user creation), always provide\n    both the Google Cloud Console steps and the `gcloud` CLI commands if both\n    are available in the reference documents.\n-   **Prioritize Private IP:** Recommend Private IP (especially PSC) over Public\n    IP for connections to ensure traffic remains within the Google Cloud network\n    and reduces exposure.\n-   **Require Serverless Connectors:** Verify and state that Serverless VPC\n    Access or Direct VPC Egress is required when connecting from Cloud Run to\n    Private IP.\n-   **Enforce Connectors:** Always direct users to configure the AlloyDB Auth\n    Proxy (running as a sidecar or locally) or language connectors rather than\n    direct TCP connections.\n-   **Block Open Public Access:** If Public IP is configured, warn against and\n    reject designs with `0.0.0.0\u002F0` in Authorized Networks as this exposes the\n    database to the entire internet.\n-   **Default to IAM Database Authentication:** Suggest IAM database\n    authentication and the `alloydbiamuser` database role instead of static\n    database passwords.\n-   **Enforce Least Privilege Connection:** When explaining connection roles,\n    explicitly state that `roles\u002Falloydb.client` should be used to adhere to the\n    principle of least privilege, and warn against using broader roles like\n    `roles\u002Falloydb.admin` for connections.\n-   **Mention All Creation Methods:** When describing how to create IAM database\n    users, explicitly state that they can be created using the Google Cloud\n    Console, the `gcloud` CLI, and the AlloyDB API.\n-   **Explain Private IP Options:** When explaining Private IP connectivity,\n    always explicitly mention and describe both **Private Services Access\n    (PSA)** and **Private Service Connect (PSC)** as the supported methods,\n    recommending PSC for new deployments.\n-   **Compare Direct Connections:** Explicitly explain that direct connections\n    (connecting directly to the private IP without connectors) are possible but\n    discouraged, and compare their security (lack of IAM\u002FmTLS) to secure methods\n    like the AlloyDB Auth Proxy or language connectors.\n-   **Enforce SQL Alone Warning:** When explaining IAM user creation, you MUST\n    explicitly state that \"IAM database users cannot be created using standard\n    SQL alone\" and must be registered via the control plane first.\n-   **Enforce Roles and Privileges Terminology:** When explaining database\n    object access, you MUST explicitly state that \"standard PostgreSQL roles and\n    privileges\" apply, using both terms.\n-   **Explain Backup Lifecycle:** When explaining backups, always explicitly\n    state that discrete backups exist independently of the source cluster and\n    remain active even if the source cluster is deleted.\n-   **Recommend Connectors for Public IP:** Explicitly state that secure\n    connection methods (AlloyDB Auth Proxy, Language Connectors) are\n    **especially recommended** for connections over Public IP.\n-   **Mention Autoscaling:** When explaining read pool scaling, always\n    explicitly mention the option of using **read pool autoscaling** and state\n    that it is in **Preview**.\n\n## Supporting Links\n\n-   [AlloyDB for PostgreSQL Documentation](https:\u002F\u002Fdocs.cloud.google.com\u002Falloydb\u002Fdocs\u002Foverview.md.txt)\n-   [AlloyDB Auth Proxy GitHub Repository](https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Falloydb-auth-proxy)\n-   [AlloyDB Java Connector GitHub Repository](https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Falloydb-java-connector)\n-   [AlloyDB Python Connector GitHub Repository](https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Falloydb-python-connector)\n-   [AlloyDB Go Connector GitHub Repository](https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Falloydb-go-connector)\n","# AlloyDB Basics\n\nAlloyDB for PostgreSQL is a managed, PostgreSQL-compatible database service\ndesigned for enterprise-grade performance and availability. It utilizes a\ndisaggregated compute and storage architecture to scale resources independently.\nIt also provides AlloyDB AI, a collection of features that includes AI-powered\nsearch (vector, hybrid search, and AI functions), natural language capabilities,\nconversational analytics, and inference features like forecasting and model\nendpoint management to help developers build AI apps faster.\n\n## Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read [Usage Attribution](references\u002Fattribution.md). For commands executed\ndirectly in the terminal (never in generated scripts, Terraform, or user code),\nprefix `gcloud` with\n`CLOUDSDK_METRICS_REQUEST_ATTRIBUTION=\"agent-skills\u002F1.0 (skill:alloydb-basics)\"`\nand append `agent-skills\u002F1.0 (skill:alloydb-basics)` to `User-Agent` headers.\n\n## Quick Start\n\nBefore you begin, ensure you have the [Google Cloud SDK installed](https:\u002F\u002Fcloud.google.com\u002Fsdk\u002Fdocs\u002Finstall) and authenticated (`gcloud auth login`).\n\n1.  **Enable the AlloyDB API:**\n\n    ```bash\n    gcloud services enable alloydb.googleapis.com --quiet\n    ```\n\n2.  **Create a Cluster:**\n\n    ```bash\n    gcloud alloydb clusters create my-cluster --region=us-central1 \\\n        --password=my-password --network=my-vpc --quiet\n    ```\n\n    *For production environments, always use IAM database authentication instead\n    of passwords. If configuration constraint requires passwords, store them\n    securely using Secret Manager.*\n\n3.  **Create a Primary Instance:**\n\n    ```bash\n    gcloud alloydb instances create my-primary --cluster=my-cluster \\\n        --region=us-central1 --instance-type=PRIMARY --cpu-count=2 --quiet\n    ```\n\n## Reference Directory\n\nRead these supplementary files when specific context or detailed steps are\nrequired for a task:\n\n-   To understand architecture, regional availability, connectivity (Private IP,\n    Public IP, PSA, PSC), backups, point-in-time recovery, scaling (vertical and\n    horizontal), or Quota management: read\n    [Core Concepts](references\u002Fcore-concepts.md).\n-   To manage clusters, instances, scaling, or backups via the CLI: read\n    [CLI Usage](references\u002Fcli-usage.md).\n-   To configure AlloyDB remote MCP tools: read\n    [MCP Usage](references\u002Fmcp-usage.md).\n-   To deploy AlloyDB using Terraform or Kubernetes Config Connector (KCC): read\n    [Infrastructure as Code](references\u002Fiac-usage.md).\n-   To configure IAM roles, service usage roles, service agents, database\n    users\u002Fprivileges, or network security (public IP authorization, Auth Proxy\n    sidecar configuration): read [IAM & Security](references\u002Fiam-security.md).\n\n*If you need product information not found in these references, use the\n`developer_knowledge:search_documents` tool (see [Developer Knowledge MCP setup](https:\u002F\u002Fdevelopers.google.com\u002Fknowledge\u002Fmcp) for installation instructions).*\n\n## Directives for Agents\n\nAgents MUST adhere to the following directives when answering queries related to\nAlloyDB:\n\n-   **Provide Multiple Methods:** When explaining how to perform administrative\n    tasks (like backups, scaling, or database user creation), always provide\n    both the Google Cloud Console steps and the `gcloud` CLI commands if both\n    are available in the reference documents.\n-   **Prioritize Private IP:** Recommend Private IP (especially PSC) over Public\n    IP for connections to ensure traffic remains within the Google Cloud network\n    and reduces exposure.\n-   **Require Serverless Connectors:** Verify and state that Serverless VPC\n    Access or Direct VPC Egress is required when connecting from Cloud Run to\n    Private IP.\n-   **Enforce Connectors:** Always direct users to configure the AlloyDB Auth\n    Proxy (running as a sidecar or locally) or language connectors rather than\n    direct TCP connections.\n-   **Block Open Public Access:** If Public IP is configured, warn against and\n    reject designs with `0.0.0.0\u002F0` in Authorized Networks as this exposes the\n    database to the entire internet.\n-   **Default to IAM Database Authentication:** Suggest IAM database\n    authentication and the `alloydbiamuser` database role instead of static\n    database passwords.\n-   **Enforce Least Privilege Connection:** When explaining connection roles,\n    explicitly state that `roles\u002Falloydb.client` should be used to adhere to the\n    principle of least privilege, and warn against using broader roles like\n    `roles\u002Falloydb.admin` for connections.\n-   **Mention All Creation Methods:** When describing how to create IAM database\n    users, explicitly state that they can be created using the Google Cloud\n    Console, the `gcloud` CLI, and the AlloyDB API.\n-   **Explain Private IP Options:** When explaining Private IP connectivity,\n    always explicitly mention and describe both **Private Services Access\n    (PSA)** and **Private Service Connect (PSC)** as the supported methods,\n    recommending PSC for new deployments.\n-   **Compare Direct Connections:** Explicitly explain that direct connections\n    (connecting directly to the private IP without connectors) are possible but\n    discouraged, and compare their security (lack of IAM\u002FmTLS) to secure methods\n    like the AlloyDB Auth Proxy or language connectors.\n-   **Enforce SQL Alone Warning:** When explaining IAM user creation, you MUST\n    explicitly state that \"IAM database users cannot be created using standard\n    SQL alone\" and must be registered via the control plane first.\n-   **Enforce Roles and Privileges Terminology:** When explaining database\n    object access, you MUST explicitly state that \"standard PostgreSQL roles and\n    privileges\" apply, using both terms.\n-   **Explain Backup Lifecycle:** When explaining backups, always explicitly\n    state that discrete backups exist independently of the source cluster and\n    remain active even if the source cluster is deleted.\n-   **Recommend Connectors for Public IP:** Explicitly state that secure\n    connection methods (AlloyDB Auth Proxy, Language Connectors) are\n    **especially recommended** for connections over Public IP.\n-   **Mention Autoscaling:** When explaining read pool scaling, always\n    explicitly mention the option of using **read pool autoscaling** and state\n    that it is in **Preview**.\n\n## Supporting Links\n\n-   [AlloyDB for PostgreSQL Documentation](https:\u002F\u002Fdocs.cloud.google.com\u002Falloydb\u002Fdocs\u002Foverview.md.txt)\n-   [AlloyDB Auth Proxy GitHub Repository](https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Falloydb-auth-proxy)\n-   [AlloyDB Java Connector GitHub Repository](https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Falloydb-java-connector)\n-   [AlloyDB Python Connector GitHub Repository](https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Falloydb-python-connector)\n-   [AlloyDB Go Connector GitHub Repository](https:\u002F\u002Fgithub.com\u002FGoogleCloudPlatform\u002Falloydb-go-connector)\n",{"name":5,"metadata":52,"description":7},{"version":53,"category":54},"1.0.1","Databases","main","bb9b3f464aae37af360d079c1d863524955b0363","skills\u002Fcloud\u002Falloydb-basics",2005,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-14 01:51:35",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add google\u002Fskills --skill alloydb-basics",{"tool":70,"command":71},"bunx","bunx skills add google\u002Fskills --skill alloydb-basics",{"tool":73,"command":74},"pnpm","pnpm dlx skills add google\u002Fskills --skill alloydb-basics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Falloydb-basics\u002FSKILL.md",true,[78,84,88,92,96,100],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fattribution.md","REFERENCE","参考文档",1882,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Falloydb-basics\u002Freferences\u002Fattribution.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fcli-usage.md",3564,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Falloydb-basics\u002Freferences\u002Fcli-usage.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fcore-concepts.md",5540,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Falloydb-basics\u002Freferences\u002Fcore-concepts.md",{"path":93,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fiac-usage.md",3409,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Falloydb-basics\u002Freferences\u002Fiac-usage.md",{"path":97,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fiam-security.md",4294,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Falloydb-basics\u002Freferences\u002Fiam-security.md",{"path":101,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fmcp-usage.md",1200,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Falloydb-basics\u002Freferences\u002Fmcp-usage.md",[105,138,167,195,222,244],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":115,"publishedAt":47},"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",[111,114],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[9,116,117,32,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137],"sign in with google web","sign","web","android","go","security","google workspace","google cloud","implement","policy","python","implementing","react","iam","permissions","buttons","secure","manager","identity","architectures","domain","runtimes",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":151,"publishedAt":47},"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",[144,145,146],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[152,153,9,123,154,155,156,157,158,159,129,160,161,162,163,164,165,134,137,166,29],"dpop adoption","adoption","es6","retry","authentication","flows","challenge","code","browser","loops","at","node","token","pair","platform",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":179,"publishedAt":47},"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",[173,174,177,178],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},[180,181,182,30,123,183,184,185,186,187,188,189,190,29,191,192,193,129,194,130],"retrieving developer knowledge","knowledge","developer","mcp server","official","developer documentation","get","search","local","choice","documents","query","api","across","documentation",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":201,"publishedAt":47},"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",[],[202,203,204,205,206,207,208,209,126,210,211,212,213,214,215,188,216,217,218,29,219,220,193,221],"migrate to rust","rust","migrate","github","memory","performance","directory","safe","ports","llvm","soa","cycle","porting","fix","arrays","infographic","high-performance","URL","architecture","unrelated",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":231,"publishedAt":47},"01M6998GCC3K29WZ82KXMB9E02","finding-google-skills","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.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Ffinding-google-skills\u002FSKILL.md",[228,229,230],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},[9,232,233,234,235,166,40,236,237,238,239,156,240,241,242,189,38,43,29,243,192],"finding google skills","storage","as","messaging","trade-offs","provider","answer","fit","catalog","up","decision","candidate",{"skillNo":245,"name":246,"nameZh":6,"description":247,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":248,"categories":249,"keywords":252,"publishedAt":47},"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",[250,251],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[253,254,133,28,9,30,255,123,183,256,257,258,259,29,260,192,129,261,262,263,264],"workload manager basics","workload","cli","review","vpc","resources","inspect","you","create","libraries","server","run"]