Agent skill · google

application-integration-troubleshooting

Diagnoses failed, stuck, or silent Google Cloud Application Integration runs and Integration Connectors tasks using the REST API, Cloud Logging, and Cloud Monitoring. Use when an integration fails, returns HTTP 200 without doing the expected work, hangs in a suspended or retry state, or hits IAM, run-as service account, connector health, or quota errors. Do not use for initial region provisioning (use application-integration-basics) or building and deploying versions (use application-integration-authoring).

What it needs

About 9k tokens when loaded.

What this skill does

Application Integration Troubleshooting Diagnose and recover Google Cloud Application Integration executions that fail, stall, or appear to do nothing. This skill walks through execution state verification, per-task failure inspection, Cloud Logging and Cloud Monitoring checks, Integration Connectors health probes, suspension resolution, and IAM or quota checks. Attribution MUST READ: Before executing any gcloud command, REST API call, or Python discovery-client call, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, ADK agents, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION="agent-skills/1.0 (skill:application-integration-troubleshooting)" and add agent-skills/1.0 (skill:application-integration-troubleshooting) to the User-Agent header of curl requests. Tooling and Scope Boundaries REST is the interface. There is no gcloud integrations command group and no Google-managed MCP server for Application Integration. Use curl with gcloud auth print-access-token, or the discovery-based Python client (googleapiclient.discovery.build("integrations", "v1") and build("connectors", "v1"); install with pip install "google-api-python-client>=2.100.0,<3" "google-auth>=2.20.0,<3") (changes host or credential state; get the user's approval first). Generic gcloud commands apply for authentication (gcloud auth), enabling APIs (gcloud services), IAM checks (gcloud projects get-iam-policy, gcloud iam service-accounts get-iam-policy), and log queries (gcloud logging read). Regional scope. Integrations, executions, connections, and execution logs live in a single Google Cloud region (LOCATION), which is the LOCATION in every REST path; no gcloud default-region setting applies. Ask the user which region the integration is deployed in. …

How to use it

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

@skills google/application-integration-troubleshooting

View the source on GitHub

Browse the @skills marketplace