Agent skill · google

api-gateway-troubleshooting

Diagnoses failing requests and deployment errors on Google Cloud API Gateway. Use when calls through a gateway return 4xx or 5xx errors, including 429 and other quota errors, time out, or fail a CORS preflight; when `api-configs create` fails with a service account, concurrency, or limit error, or `gateways create` or `gateways update` fails; when a custom domain, load balancer, or TLS finding involves a gateway; or when the user asks if Google is at fault. Don't use for Apigee, Cloud Endpoints, or GKE Gateway API. For OpenAPI errors from `api-configs create`, use api-gateway-openapi-spec-authoring; for setting up or changing API keys, JWTs, or quotas, use api-gateway-backend-security-and-rate-limiting; for MCP `/mcp` errors, use api-gateway-mcp-server.

What it needs

About 11k tokens when loaded.

What this skill does

API Gateway Troubleshooting Use this skill to find out why requests to a deployed Google Cloud API Gateway fail and how to fix them. Work only from three sources of evidence: 1. Public Google Cloud documentation, linked from this skill. 2. The user's own project, read with the user's own credentials. 3. Files and output that the user provides, such as an OpenAPI document, an error response, or a pasted log entry. Scope This skill covers only Google Cloud API Gateway. If the question is about Apigee, Cloud Endpoints, or GKE Gateway API, reply that this skill covers only Google Cloud API Gateway, and don't run its steps or commands. Usage Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution. Ground rules Rule Why :--- :--- Stay read-only until the user approves a change. While you diagnose, run only list, describe, get-iam-policy, and logging read commands, plus nslookup and curl GET requests to a path that's safe to call. Gateways serve production traffic, and the quota metrics and limits of the most recently created API config apply to every gateway of the API. Before any change, show the exact command, what it changes, and how to undo it, then wait for an explicit yes. Changes include IAM grants, api-configs create, gateways update, Cloud Run ingress changes, and gcloud services enable. The user owns the project and the change. Never fix a 401 or 403 by making a backend public (--allow-unauthenticated, --no-invoker-iam-check, allUsers) or by granting a basic role such as Editor. Grant the gateway's service account the invoker role on the one backend instead, which keeps least privilege. Keep every log read bounded: filter on the gateway, set --freshness or a timestamp window, and set --limit. Unbounded reads are slow and pull in caller data that the diagnosis doesn't need. Redact API keys, bearer tokens, and JWTs before you show log entries, commands, or files. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/api-gateway-troubleshooting

View the source on GitHub

Browse the @skills marketplace