API Gateway Troubleshooting
GoogleOfficialPublished by Google
- Skill
- Tool integration
- Cloud and DevOps
- Apache-2.0
- Low risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured, evidence-based workflow for troubleshooting Google Cloud API Gateway. It helps identify the root cause of 4xx and 5xx errors, deployment failures, and configuration issues by analyzing logs, checking project configurations, and validating OpenAPI specifications. The skill emphasizes safe, read-only diagnostic practices and requires explicit user approval before applying any changes to the infrastructure.
What it does
- Identifies the specific hop (gateway or backend) where a request is failing.
- Analyzes gateway logs to pinpoint authentication, quota, or routing errors.
- Validates OpenAPI specifications using an offline linter to prevent deployment errors.
- Provides step-by-step guidance for resolving IAM, service account, and configuration issues.
- Offers a clear escalation path for issues originating within the Google Cloud platform.
- Enforces safe operational habits by requiring approval for all configuration changes.
When to use it
- When API Gateway returns 4xx or 5xx errors, including 429 quota errors or CORS failures.
- When deployment commands like api-configs create or gateways update fail.
- When investigating issues with custom domains, load balancers, or TLS configurations.
- When you need to verify if a failure is caused by the gateway, the backend, or the caller's credentials.
Advantages
- Reduces downtime by systematically isolating the source of API failures.
- Prevents accidental configuration changes through a strict approval-based workflow.
- Ensures security by mandating the redaction of sensitive credentials from logs and output.
- Provides consistent, documented troubleshooting steps aligned with official Google Cloud practices.
Usage examples
- “My API Gateway is returning 500 errors for all requests. Can you help?”
- The agent will collect the project ID and gateway details, then use the provided log query to identify if the error is a gateway-side issue or a backend failure.
- “I am getting a 403 error when calling my API through the gateway.”
- The agent will determine if the 403 is coming from the gateway (auth/API key) or the backend (IAM/invoker role) and guide you through the appropriate fix.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/google/api-gateway-troubleshooting/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip api-gateway-troubleshooting.zip -d .agents/skills
Documentation by Google
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:
Public Google Cloud documentation, linked from this skill.
The user's own project, read with the user's own credentials.
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. | Request logs and pasted output can contain credentials. |
| Base every limit, default, and error meaning on a linked public doc or on output from the user's project. If neither explains the problem, say so and escalate. | Guessing about undocumented behavior leads to wrong fixes. |
Use the user's existing gcloud login. Never ask for passwords, API key values, or service account key files. | Credentials don't belong in a chat transcript. |
| For Preview features (streaming, MCP, model routing), check the release notes before answering. | Preview behavior changes between releases. |
Prerequisites
Google Cloud CLI. Use a recent
gcloud(the commands here were checked with version 591.0.0); see Install the gcloud CLI. Don't install or update software without the user's approval. Ifgcloudisn't available or the user says not to run commands, work in evidence mode: give the user the read-only commands to run, and diagnose from the output, response bodies, and log entries they paste.Authentication. Use the user's existing
gcloud auth loginsession; this skill doesn't need application-default credentials.Project. Ask which project hosts the gateway and pass
--project={project_id}on every command. Don't rungcloud config set, because it changes the user's environment. This skill troubleshoots existing gateways and never creates projects.Billing. The project needs an active billing account even when usage stays in the free tier; see API Gateway pricing.
APIs. API Gateway requires
apigateway.googleapis.com,servicemanagement.googleapis.com, andservicecontrol.googleapis.com. A gateway can keep responding while one of them is missing, and its logs then stay empty, so check withgcloud services list --enabled --project={project_id}. Enabling a missing API is a change that needs approval.IAM roles for diagnosis (read-only):
roles/apigateway.viewer,roles/logging.viewer,roles/serviceusage.serviceUsageViewer, androles/iam.serviceAccountViewer(to check the gateway's service account). For Cloud Run backends, addroles/run.viewer; to trace a custom domain through its load balancer, addroles/compute.viewer; to check an API key's project,roles/serviceusage.serviceUsageVieweris also needed there.IAM roles for fixes (only after approval):
roles/apigateway.admin;roles/iam.serviceAccountUseron the gateway's service account, because creating or updating an API config or a gateway requiresiam.serviceAccounts.actAs;roles/run.adminto change a Cloud Run service's IAM policy or ingress;roles/serviceusage.serviceUsageAdminto enable an API or a managed service, plusroles/servicemanagement.serviceConsumeron the API's managed service to enable it in another project; androles/iam.serviceAccountAdminto re-enable a disabled service account.Region. Gateways are regional. Use the region that
gateways listreports. When a fix needs a new gateway, create it in the original gateway's region, or inus-central1if the user has no preference; see API Gateway deployment model and Cloud locations.
Workflow
Copy this checklist into your notes and tick it off as you go:
- [ ] 1. Context collected
- [ ] 2. Gateway identified by defaultHostname
- [ ] 3. Expected or transient states ruled out
- [ ] 4. Gateway log entry read (bounded query)
- [ ] 5. One branch chosen from the classification table
- [ ] 6. Root cause stated with redacted evidence and a doc link
- [ ] 7. Fix proposed, approved, and applied (or handed to the user)
- [ ] 8. Fix verified
- [ ] 9. Escalated, if the evidence points to Google Cloud1. Collect context
Extract these from the conversation first, and ask only for what's missing:
| Needed | Why |
|---|---|
{project_id} of the gateway | Every command is scoped to it. |
Failing URL (host and path) or {gateway_id} and {region} | Identifies the gateway. |
| HTTP method, status code, and response body | Separates gateway errors from backend errors. |
| Approximate time of the failure, in UTC | Bounds the log query. |
| What changed recently (new API config, IAM, backend deploy, DNS) | Recent changes are the first place to look. |
| Authentication used by the caller (API key, JWT, none) | Selects the auth branch. |
If the project or the host is unknown, stop and ask before you run any
gcloud command. Don't guess project IDs, and don't use the active gcloud
project instead.
2. Identify the gateway
List the project's gateways:
gcloud api-gateway gateways list --project={project_id} \
--format="table(name.basename():label=GATEWAY,name.segment(3):label=REGION,defaultHostname,state,apiConfig)"Match the request host against defaultHostname. Don't decide from the URL
suffix: a gateway's hostname can use either of two gateway.dev formats or,
for older streaming and model-routing gateways, a run.app format. Don't
guess the owning project from numbers in the hostname either; list the
gateways in the project the user names. A custom domain points at a load
balancer whose serverless NEG targets the gateway. See
references/triage-and-logs.md for the
hostname formats and how to trace a custom domain.
If no gateway in the project matches, confirm the product before going on (see Scope).
Then read the gateway's details, including its API config and streaming mode:
gcloud api-gateway gateways describe {gateway_id} \
--location={region} --project={project_id}3. Rule out expected and transient states
Gateway
stateisn'tACTIVE:CREATINGorUPDATINGmeans an operation is still running, so wait and check again.FAILEDmeans creation failed; read the error of the failed operation.DELETINGmeans the gateway is being removed.API config just created: creating a complex API config can take up to ten minutes, and only one config can be created for an API at a time.
First requests after an idle period: API Gateway has cold-start latency.
Google Cloud incident: check the Service Health dashboard.
4. Read the gateway log entry
Use a bounded query that prints only the fields you need. Replace
{status_code} with the status the caller saw:
gcloud logging read 'resource.type="apigateway.googleapis.com/Gateway" AND resource.labels.gateway_id="{gateway_id}" AND resource.labels.location="{region}" AND httpRequest.status={status_code}' \
--project={project_id} --freshness=1h --limit=20 \
--format="json(timestamp,httpRequest.status,httpRequest.latency,httpRequest.requestUrl,jsonPayload.responseDetails,jsonPayload.apiConfig,jsonPayload.apiMethod)"If you know the failure time, replace --freshness with a
timestamp>="{start_utc}" AND timestamp<="{end_utc}" filter that spans about
30 minutes around it. Read httpRequest.status, httpRequest.requestUrl,
jsonPayload.responseDetails, jsonPayload.apiConfig, and
jsonPayload.apiMethod. Keep the --format field list, because a full entry
can contain the caller's credentials, and redact credentials before you quote
any field, including a key query parameter in httpRequest.requestUrl.
To compare API configs, compare only the apis/{api_id}/configs/{config_id}
part: the same config can appear as a full resource name
(//apigateway.googleapis.com/projects/...) and with either the project
number or the project ID.
jsonPayload.responseDetails decides the branch: via_upstream means the
backend produced the response; any other value means the gateway produced it.
The troubleshooting page explains via_upstream and
service_control_quota_error, and the model routing page explains the
model_router_* values that model-routing gateways log. Quote any other value
as-is, and don't explain how the gateway works internally.
5. Classify and follow one branch
Pick the first row that matches, and load only the reference file it names.
| What you see | Likely cause | Reference |
|---|---|---|
401 or 403 with via_upstream | The backend rejected the gateway: invoker role, audience, or deleted service account | auth-errors.md |
A 4xx produced by the gateway whose body names a credential problem (for example UNAUTHENTICATED) | The API key or JWT was rejected; quote the body | auth-errors.md |
500 with no gateway log entry, after log exclusions and a wrong scope are ruled out | The gateway's service account may be deleted or disabled | auth-errors.md |
500 with service_control_quota_error | Quota metric missing from the newest API config | config-deployment-errors.md |
429 with service_control_quota_error | The caller exceeded the API's quota | limits-and-escalation.md |
404, 502, 503, or 504, an oversized request, or a timeout | Routing, backend errors, size limits, or the deadline. The docs don't name the status codes for size or deadline failures, so confirm with responseDetails and the body. | backend-routing-and-timeouts.md |
| CORS preflight fails or latency is high | CORS pass-through or slow backend | backend-routing-and-timeouts.md |
api-configs create fails with an error about the OpenAPI document, such as an unsupported extension or an invalid path, parameter, server, or security requirement | A spec problem | Hand off to api-gateway-openapi-spec-authoring; if it isn't installed, see OpenAPI pre-flight check |
api-configs create fails with a service account, concurrency, or limit error, or gateways create or gateways update fails | Service account, concurrent creates, limits, or the backend deadline | config-deployment-errors.md |
400 "The request was malformed" from an old TLS client, TLS scan findings, custom domain, or no log entry at all | TLS enforcement, DNS, load balancer, or wrong host | networking-domains-tls.md |
| Errors on several gateways, or on an unchanged config, with healthy backends | Possible Google Cloud issue | limits-and-escalation.md |
If the request also needs log queries or backend inspection commands, use triage-and-logs.md.
6. State the root cause
Give the cause, the evidence (redacted, quoted verbatim from logs or command output), and the public doc section that explains it. If the evidence fits more than one cause, list at most three, say what would tell them apart, and collect that evidence before proposing a fix.
7. Propose the fix
Show the exact command, the resource it changes, its effect on live traffic, and how to undo it. Wait for approval, then run it, or hand it to the user if they prefer. Keep these rules in mind:
To change the OpenAPI document, create a new API config and deploy it with
gcloud api-gateway gateways update. Before you create the config, check quota metrics with theapi-gateway-backend-security-and-rate-limitingskill, because the newest API config's quota metrics apply to every gateway of the API.Before you create a new API config, check the OpenAPI document with the linter (see OpenAPI pre-flight check).
8. Verify
Read the logs again for new entries after the change, or repeat the failing
request. Repeat a request yourself only if it's safe to repeat, such as a
GET; otherwise ask the user to repeat it, because a repeated POST can
change data in their backend. After gateways update, wait until the
gateway's state is ACTIVE before you test.
9. Escalate when the evidence points to Google Cloud
Escalate to Cloud Customer Care when the
service account is active, the required APIs are enabled, and no log exclusion
or wrong scope explains it, but requests get 500 errors with no gateway log
entry; when several gateways fail at once without a config change; when errors
are intermittent on an unchanged config while the backend logs stay clean;
when control-plane operations keep failing with internal errors; or when
Service Health reports an incident. Draft the case text with the evidence
bundle in limits-and-escalation.md. The
user files the case.
OpenAPI pre-flight check
Run the linter on every OpenAPI file before creating an API config. Run it; don't read its source. If you don't have the file, give the user the command to run:
python3 scripts/lint_openapi_for_gateway.py {spec_path} [{spec_path} ...]It reads the files only, makes no network calls, and prints JSON findings that
each link to the public doc for the limitation. Exit code 0 means no errors,
1 means at least one ERROR finding, and 2 means a usage, parse, or
dependency error. The linter needs Python 3.8 or later. YAML input needs
PyYAML; ask the user before you install it with
pip install "PyYAML>=6.0,<7.0". JSON input doesn't. Fix the ERROR
findings, and then create the API config. If api-configs create still fails
on the OpenAPI document, hand off to api-gateway-openapi-spec-authoring, or
use the error message if that skill isn't installed. Show WARNING findings
to the user and explain them.
Output format
Report findings in this form:
**Problem:** <one sentence in the user's terms>
**Failed hop:** <gateway or backend, and the evidence for it>
**Evidence:** <redacted log fields or command output, verbatim>
**Root cause:** <one or two sentences> (<public doc link>)
**Fix:** <exact command or spec change; approval needed: yes/no>
**Verify:** <how to confirm the fix>
**Open questions:** <anything you couldn't confirm>Related skills
| Need | Skill |
|---|---|
| Write or change API key, JWT, backend authentication, or quota configuration | api-gateway-backend-security-and-rate-limiting |
Write, migrate, or fix an OpenAPI spec, including OpenAPI errors from api-configs create | api-gateway-openapi-spec-authoring |
MCP /mcp JSON-RPC errors on an MCP-enabled gateway | api-gateway-mcp-server |
| Deep IAM analysis, such as deny policies or role discovery | iam-helper-for-troubleshooting |
| Build a load balancer, Cloud Armor policy, or custom domain front end | google-cloud-global-frontend-configuration |
| Deploy or reconfigure a Cloud Run backend | cloud-run-basics |
Reference files
references/attribution.md: usage attribution rules for every command you run.
references/triage-and-logs.md: hostname formats, log queries, log fields, metrics, and backend inspection commands.
references/auth-errors.md:
401and403on either hop, API keys, JWTs, and the gateway service account.references/backend-routing-and-timeouts.md:
404, size limits, backend5xx,504and deadlines, CORS, and streaming.references/config-deployment-errors.md: API config and gateway create, update, and delete failures other than OpenAPI errors, and quota metric conflicts.
references/networking-domains-tls.md: custom domains, load balancers, TLS, and requests that never reach the gateway.
references/limits-and-escalation.md: product limits, quota increases, unsupported features, and the Cloud Customer Care evidence bundle.
scripts/lint_openapi_for_gateway.py: offline linter for documented OpenAPI limitations.
Files
- ATTRIBUTION.mdAdded by AutoGineer872 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md19.2 KiB
- references/attribution.md1.9 KiB
- references/auth-errors.md10.2 KiB
- references/backend-routing-and-timeouts.md7.4 KiB
- references/config-deployment-errors.md4.9 KiB
- references/limits-and-escalation.md4.4 KiB
- references/networking-domains-tls.md4.8 KiB
- references/triage-and-logs.md7.6 KiB
- scripts/lint_openapi_for_gateway.pyScript25.0 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an API key, Needs a command-line tool, Needs Python
Security
What our scanner noticed· Low risk
- Instructions that use the network
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Publisher
- Google (Official)
- Source
- google/skills · skills/cloud/api-gateway-troubleshooting · commit 2194d3b
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download api-gateway-troubleshooting.zip