Terminal
Terminal/Skill
Searches official Google developer documentation and returns answers and exact commands, via an MCP server or REST API.
By Google
Works with
npx skills add google/skills --skill retrieving-developer-knowledgeThe 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.
answer_query (for conceptual guides/workflows) or search_documents (for CLI flags/syntax).curl against https://developerknowledge.googleapis.com/v1.answer_query, search_documents or get_documents tool at all, even though the plugin declares one. Treat their absence as normal and use the REST fallback below.PERMISSION_DENIED, 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.
answer_query or the REST :answerQuery endpoint returns an HTTP 429 (RESOURCE_EXHAUSTED / out of quota error), this indicates server-side generative QA quota exhaustion. Do not treat this as an unrecoverable failure or fall back to ungrounded memory; immediately retry using the search endpoint (search_documents for MCP, or documents:searchDocumentChunks for REST) with 2–5 focused keywords from the query.Choose the appropriate tool based on availability in your runtime environment:
When MCP tools are present in your active tool definitions:
answer_query(query="..."): Use for conceptual guides, architectural comparisons, product choice overviews, and multi-step workflows. This tool has limited quota. If you get a 429 out of quota error, use search_documents instead.search_documents(query="..."): Use for granular CLI flags, exact syntax, parameter names, and IAM permissions (service.resource.verb). Use 2–5 focused keywords (e.g., cloud run filestore nfs mount gcloud) rather than full conversational sentences.get_documents(names=["documents/{uri_without_scheme}"]): Fetch full documentation pages by resource name (e.g. names: ["documents/docs.cloud.google.com/run/docs/overview/what-is-cloud-run"]).When the MCP tools are absent, query the Developer Knowledge REST API
(https://developerknowledge.googleapis.com/v1) with curl. Two credentials
work, and you should try them in this order.
An existing Google credential, preferred. If gcloud is authenticated,
pass a bearer token and your quota project. Nothing needs to be installed or
configured:
curl -s -X POST "https://developerknowledge.googleapis.com/v1:answerQuery" \
-H "Authorization: Bearer $(gcloud auth print-access-token)" \
-H "X-Goog-User-Project: $(gcloud config get-value project 2>/dev/null)" \
-H "Content-Type: application/json" \
-d "{\"query\": \"How do I configure public read access on Cloud Storage?\"}"
If that fails to authenticate, on a 401, a 403, or any other credential error,
the account has a token the API will not accept. Substitute
gcloud auth application-default print-access-token for
gcloud auth print-access-token in the command above and try again. Which
credential the API accepts depends on how the environment was authenticated, so
treat an auth error here as a reason to try the application-default credential
rather than as a failed lookup.
An API key, if one is configured. Where DEVELOPERKNOWLEDGE_API_KEY is set
in the environment, pass it as a key query parameter instead of an
Authorization header. If neither credential is available, an API key is the
supported path for this client: enable the API and create one by following the
Developer Knowledge quickstart,
then export it as DEVELOPERKNOWLEDGE_API_KEY. Say that you need a credential
rather than answering without a lookup. The remaining examples in this section
use that form:
curl -s -X POST "https://developerknowledge.googleapis.com/v1:answerQuery?key=${DEVELOPERKNOWLEDGE_API_KEY}" \
-H "Content-Type: application/json" \
-d '{"query": "How do I configure public read access on Cloud Storage?"}'
This endpoint has limited quota. If you get a 429 out of quota error, use documents:searchDocumentChunks instead.curl -s "https://developerknowledge.googleapis.com/v1/documents:searchDocumentChunks?query=gcloud+logging+metrics+create&key=${DEVELOPERKNOWLEDGE_API_KEY}"
curl -s "https://developerknowledge.googleapis.com/v1/documents/docs.cloud.google.com/run/docs/overview/what-is-cloud-run?key=${DEVELOPERKNOWLEDGE_API_KEY}"
GET, with one names parameter per document and no
request body; up to 20 per call):
curl -s -G "https://developerknowledge.googleapis.com/v1/documents:batchGet" \
--data-urlencode "names=documents/docs.cloud.google.com/run/docs/overview/what-is-cloud-run" \
--data-urlencode "names=documents/docs.cloud.google.com/storage/docs/creating-buckets" \
--data-urlencode "key=${DEVELOPERKNOWLEDGE_API_KEY}"
location=IP:PATH), and IAM permission strings according to official Google specifications.PROJECT_ID, SERVICE_NAME, REGION) directly in your final message, even if previously referenced during internal planning.