Agent skill · google
retrieving-developer-knowledge
Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, 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.
What it needs
About 3k tokens when loaded.
What this skill does
Google Developer Knowledge The Developer Knowledge skill provides access to official Google developer documentation across Google Cloud, AI/ML (ai.google.dev, ADK, TensorFlow), Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms via the Developer Knowledge MCP server or REST API fallback. Workflow 1. Direct Retrieval: When answering a technical question, execute a single documentation lookup directly within your current conversation context (do not delegate retrieval to subagents): If MCP tools are present in your environment: Call answerquery (for conceptual guides/workflows) or searchdocuments (for CLI flags/syntax). If MCP tools are not present: Execute a REST API request via curl against https://developerknowledge.googleapis.com/v1. A declared server is not always a connected server. Some clients cannot complete the MCP handshake with this server and expose no answerquery, searchdocuments or getdocuments tool at all, even though the plugin declares one. Treat their absence as normal and use the REST fallback below. 2. Confirm the lookup succeeded before using it: A response that arrives is not automatically an answer. PERMISSIONDENIED, UNAUTHENTICATED, HTTP 401 or 403, an empty result set, or any error payload is a FAILED lookup even when the tool itself reported no error. On a failed lookup, do not answer as though it had succeeded. Try the other transport once, and if that also fails, state plainly in your reply to the user that you could not reach Developer Knowledge and are answering without it. Presenting recalled documentation as a retrieved result is the worst available outcome, because nothing in the reply distinguishes it from a real lookup. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/retrieving-developer-knowledge