retrieving-developer-knowledge

Search and retrieve official Google developer documentation across Cloud, AI, Android, Web, and Firebase platforms.

23.7k|2.0k|Updated Mar 31, 2026
Ready to run
npx skills add https://github.com/google/skills --skill retrieving-developer-knowledge-google
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: retrieving-developer-knowledge
Source: https://github.com/google/skills/tree/main/plugins/cloud/google-cloud-developer/skills/retrieving-developer-knowledge
Command: npx skills add https://github.com/google/skills --skill retrieving-developer-knowledge-google

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, and includes references (resource) components.

What problem does it solve? Finding authoritative Google documentation across fragmented domains—Cloud CLI syntax, IAM permissions, API parameters, architectural guidance—requires switching between multiple sites and searching individually. This Skill centralizes retrieval through a unified API, eliminating guesswork and ensuring grounding in official sources. ## Core Features & Use Cases - Unified Documentation Search: Query gcloud CLI flags, REST API syntax, IAM permissions, and architectural comparisons across Google Cloud, Gemini, Android, Firebase, Flutter, and Web platforms from a single interface. - Fallback REST API Integration: When MCP tools are unavailable, use curl with OAuth tokens or API keys to retrieve documentation without external dependencies. - Synthesis with Source Attribution: Ground technical solutions directly in retrieved documentation with exact parameter formatting and complete commands. - Use Case: A developer needs the exact gcloud command to mount an NFS filestore on Cloud Run with all required flags. Rather than piecing together multiple docs pages, request the documentation lookup and receive the complete, tested command with parameter descriptions. ## Quick Start When you need official Google documentation for any task—such as configuring IAM roles in Cloud, deploying a service on Cloud Run, or using the Gemini API—ask for a documentation lookup and the Skill will retrieve the authoritative answer with exact syntax and required parameters.

Frequently Asked Questions about retrieving-developer-knowledge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the exact gcloud CLI syntax for a specific command?▼

Use search_documents with focused keywords (e.g., 'gcloud run deploy environment variables') to retrieve official documentation chunks showing parameter names, flags, and usage examples. The REST fallback curl command works identically when MCP tools are unavailable.

What are the required IAM permissions to deploy to Cloud Run?▼

Search for 'Cloud Run IAM roles permissions deploy' to retrieve the service.resource.verb formatted permission strings from official Google Cloud documentation. The response includes all required and optional roles for deployment, scaling, and traffic configuration.

Does Developer Knowledge cover Gemini API documentation?▼

Yes. The Skill searches ai.google.dev, adk.dev, and geminicli.com domains. Use answer_query for conceptual guides on model capabilities and search_documents for specific API parameter names and request formats.

What should I do if the REST API returns a 429 quota error?▼

HTTP 429 indicates generative QA quota exhaustion on answer_query. Immediately retry using search_documents with 2-5 focused keywords instead; the search endpoint has separate quota and returns syntax examples without synthesis.

Can I use this Skill to retrieve documentation for non-Google platforms?▼

No. The Skill searches only official Google developer domains (docs.cloud.google.com, ai.google.dev, developer.android.com, etc.). For third-party documentation, use a general search Skill or manual lookups.

How do I authenticate the REST API without gcloud installed?▼

If gcloud is unavailable, enable the Developer Knowledge API and create an API key from the Google Cloud Console. Export it as DEVELOPERKNOWLEDGE_API_KEY and pass it as a query parameter (?key=...) in curl requests.