Overview
This repository contains a collection of reusable Agent Skills for Google products and cloud technologies. It enables developers to quickly add capabilities like Gemini API, BigQuery basics, and Cloud Run to their agents.
README Preview
# Agent Skills\n\n[](https://skills.sh/google/skills)\n\nThis repository contains [Agent Skills](https://agentskills.io/home) for Google\nproducts and technologies, including [Google Cloud](https://cloud.google.com).\n\n> [!NOTE]\n> This repository is under active development.\n\n## Installation\n\n```bash\nnpx skills add google/skills\n```\n\nFrom the `npx install` command, you can select the specific skills from this\nrepo to install.\n\n## Available Skills\n\n- [**Gemini API on Agent Platform**](./skills/cloud/gemini-api)\n- [**Gemini Interactions API on Agent Platform**](./skills/cloud/gemini-api)\n- [**Managed Agents API on Agent Platform**](./skills/cloud/gemini-agents-api)\n- [**Skill Registry API on Agent Platform**](./skills/cloud/agent-platform-skill-registry)\n- [**AlloyDB Basics**](./skills/cloud/alloydb-basics)\n- [**BigQuery Basics**](./skills/cloud/bigquery-basics)\n- [**Cloud Run Basics**](./skills/cloud/cloud-run-basics)\n- [**Cloud SQL Basics**](./skills/cloud/cloud-sql-basics)\n- [**Firebase Basics**](./skills/cloud/firebase-basics)\n- [**Kubernetes Engine (GKE) Basics**](./skills/cloud/gke-basics)\n- [**Recipe: Onboarding to Google Cloud**](./skills/cloud/google-cloud-recipe-onboarding)\n- [**Recipe: Authenticating to Google Cloud**](./skills/cloud/google-cloud-recipe-auth)\n- [**Recipe: Google Cloud Network Observability**](./skills/cloud/google-cloud-networking-observability)\n- **Google Cloud Well-Architected Framework**:\n - [Security](./skills/cloud/google-cloud-waf-security)\n - [Reliability](./skills/cloud/google-cloud-waf-reliability)\n - [Cost optimization](./skills/cloud/google-cloud-waf-cost-optimization)\n - [Operational excellence](./skills/cloud/google-cloud-waf-operational-excellence)\n - [Performance optimization](./skills/cloud/google-cloud-waf-performance-optimization)\n - [Sustainability](./skills/cloud/google-cloud-waf-sustainability)\n\n## Support\n\nIf you need help or encounter
FAQ (3)
TroubleshootingHow to fix "Nested mappings are not allowed in compact mappings" YAML parse error when installing the google-ads-api-account-diagnostics skill?
This error occurs because the compatibility line in skills/ads/google-ads-api-account-diagnostics/SKILL.md frontmatter contained an unquoted colon (tools: search, ...), which YAML interprets as a nested mapping. The bug was introduced in commit 300d74bfee and fixed in commit 6f82b205c0acbe185ce513ce0390bc4b57caa877. Update to the latest version of the google/skills repository, then rerun: npx skills add google/skills --skill google-ads-api-account-diagnostics -g -y. If you maintain your own SKILL.md and hit this error, quote any frontmatter value containing a colon, e.g. compatibility: "Google Ads MCP Server (tools: search, list_accessible_customers, get_resource_metadata); ...".
TroubleshootingHow do I fix the google-cloud-developer Developer Knowledge MCP server showing "Failed to connect" or missing authentication credentials in Claude Code?
The Claude Code plugin's mcp.json registers https://developerknowledge.googleapis.com/mcp without an API key header or OAuth configuration, while tool calls require Google authentication.
Workaround: register the MCP server yourself with an API key restricted to developerknowledge.googleapis.com:
claude mcp add --transport http --scope user google-dev-knowledge \
https://developerknowledge.googleapis.com/mcp \
--header "X-Goog-Api-Key: YOUR_API_KEY"The --header option must appear after the server name and URL. Restart Claude Code and verify with:
claude mcp listThe plugin's bundled developer-knowledge entry may still display "Failed to connect," but it is harmless; the plugin skills can use your separately registered google-dev-knowledge server.
For testing only, the endpoint also accepts a short-lived gcloud token:
curl -X POST https://developerknowledge.googleapis.com/mcp \
-H "Authorization: Bearer $(gcloud auth print-access-token)" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'A permanent plugin fix would be to add an env-expanded X-Goog-Api-Key header to mcp.json, support OAuth discovery, or remove the unauthenticated server entry and use the curl fallback.
TroubleshootingWhy do relative Markdown links inside a references/ directory 404 as references/references/ on GitHub?
Because the linking file is already inside references/, a link such as [Guide](references/ima-sdk-ios-guide.md) resolves to references/references/ima-sdk-ios-guide.md. Remove the references/ prefix and link directly to the sibling file: [Guide](ima-sdk-ios-guide.md). Find broken links with:
grep -rnE '\]\(references/' skills/*/*/references/*.mdApply the fix in each affected file, for example:
<!-- Before -->
[iOS Guide](references/ima-sdk-ios-guide.md)
<!-- After -->
[iOS Guide](ima-sdk-ios-guide.md)A batch replacement can be run with:
find skills -path '*/references/*.md' -exec perl -pi -e 's/\]\(references\//](/g' {} +The target files do not need to be moved; only the link prefix is incorrect. This issue was fixed in commit a54d506fb1ae95870e10cbf5cf1660f3af0bdc8b.