Skip to content
Get packs

Guide · Agent skill

How to use the Application Integration Troubleshooting agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The Application Integration Troubleshooting skill is a set of instructions and reference files that an AI agent can load to investigate Google Cloud Application Integration workflows that fail, hang in a suspended or retry state, or return success without doing their work. It also covers Integration Connectors tasks that return errors or unhealthy status. This guide explains what agent skills are, how to install this one, how to ask for it, and how to keep its checks safe. After reading, you will be able to set it up and run a read-first investigation of a failing integration.

Application Integration Troubleshootinggoogle/skills · Apache-2.0

Quick start

  1. 1Download and unzip the skill. Download the ZIP from this page and unzip it. Place the folder in ~/.claude/skills/ or in your project's .claude/skills/ folder, or upload the ZIP under Settings → Capabilities → Skills.
  2. 2Confirm your gcloud identity and project. Run gcloud config get-value account and gcloud config get-value project to verify who you are and which project is active.
  3. 3Check the required APIs. Confirm that Application Integration and Integration Connectors APIs are enabled on your project. Ask before enabling any missing API.
  4. 4Describe the failing integration. Tell the agent the symptom, the integration name and the project. Include the region if you know it.
  5. 5Review the read-only findings. Let the agent list executions and read task states, logs and connector health before deciding on any fix.
  6. 6Approve any state change explicitly. If a fix requires canceling a run, lifting a suspension or changing IAM, read the exact command and approve it only if you agree.

What is an agent skill and what does this one do?

An agent skill is a folder of instructions, reference files and sometimes scripts that an AI agent reads when a task matches the skill's description. This skill is for diagnosing Application Integration problems. It follows a fixed checklist: it checks whether an execution actually ran and what state each task reached, inspects logs and monitoring, probes Integration Connectors health, and checks IAM, run-as service account and quota problems.

Read-only checks run freely. Changes such as canceling runs, lifting suspensions, or installing packages require your explicit approval first.

  • Confirms whether an execution ran and reads each task's state rather than trusting an HTTP 200 response.
  • Reads Cloud Logging and Cloud Monitoring for failures.
  • Checks Integration Connectors connection and eventing health.
  • Checks IAM, service account and quota causes of 403 and related errors.

Install the skill from the ZIP or the Claude apps

Download the ZIP from this page and unzip it. For a personal setup, place the unzipped folder in ~/.claude/skills/. For a single project, place it in the project's .claude/skills/ folder.

If you use the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.

  • Personal install: ~/.claude/skills/
  • Project install: .claude/skills/ inside your project
  • Claude apps: Settings → Capabilities → Skills

Check what you need before you start

The skill needs the Google Cloud SDK (gcloud) with an authenticated identity that can access the target project. It also uses curl with a token from gcloud auth print-access-token. The Application Integration and Integration Connectors APIs must be enabled on the project, and the project needs an active billing account. You also need permission to read executions, suspensions, connections, logs and IAM policies.

Python is optional. The google-api-python-client and google-auth packages are only needed for the discovery-based Python client, and the skill installs them only with your approval.

  • gcloud with an authenticated identity and project access
  • curl and a token from gcloud auth print-access-token
  • Application Integration and Integration Connectors APIs enabled, with an active billing account
  • Read permissions for executions, suspensions, connections, logs and IAM policies
gcloud config get-value account gcloud config get-value project

Trigger the skill with natural requests

You do not need to name the skill. Describe the symptom and mention the integration. The skill's description covers failed runs, silent successes, suspended or retrying executions, connector health problems, and IAM, service account or quota errors.

Have the region ready. Integrations live in a single Google Cloud region, and the skill will ask which one it is deployed in. If you do not know, it starts with us-central1 and then checks the other Application Integration locations.

  • "My order-sync integration in project my-project failed last night. Find out why."
  • "This integration returns 200 but nothing is written to the database. Check whether the tasks actually ran."
  • "The execution has been suspended for two hours. What is blocking it?"
  • "My Salesforce connector task is returning errors. Is the connection healthy?"

Safety: scripts, network and approvals

This skill runs scripts and uses the network. It calls Google Cloud APIs and reads logs. It will not delete integrations, versions, connections or auth profiles unless you specifically ask. Before canceling or replaying an execution, lifting a suspension, changing IAM bindings, installing pip packages, or changing gcloud configuration or credentials, it shows the exact command and waits for your approval.

Review each command before you approve it, especially anything that changes state or credentials.

  • Read-only: executions list, suspensions list, connection reads, gcloud logging read.
  • Needs approval: cancel or replay, lift suspension, pip install, gcloud config set, application-default login.

What people use it for

  • Finding out why a nightly integration failed in production and which task raised the error.
  • Checking whether an integration returning HTTP 200 actually completed its tasks.
  • Diagnosing a suspended execution that has been waiting for a long time.
  • Investigating a Connectors task that returns errors or an unhealthy connection status.
  • Ruling out IAM, run-as service account or quota causes before changing a live integration.

Frequently asked questions

How do I install the application integration troubleshooting skill?

Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.

What do I need to use this skill?

You need the Google Cloud SDK (gcloud) with an authenticated identity that can access the project, curl, and the Application Integration and Integration Connectors APIs enabled. The project also needs an active billing account and permission to read executions, logs, connections and IAM policies.

Is this skill free to use?

The skill is published under the Apache-2.0 licence. Google Cloud usage is separate: the source notes that an active billing account is required even when usage stays within the monthly free tier, so check the Application Integration pricing page for costs.

Does the skill change my live integrations?

Not by default. Read-only checks run freely, but canceling or replaying runs, lifting suspensions, refreshing connector metadata, changing IAM and installing packages all require your explicit approval first.

Can it fix a suspended integration automatically?

No. The skill shows the exact command needed to lift or resolve a suspension and waits for your approval before running anything that changes state.

How is this different from the basics and authoring skills?

This skill only troubleshoots failing, stuck or silent runs. Initial region setup and API enablement belong to application-integration-basics, and building, editing or publishing integrations belongs to application-integration-authoring.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

This skill suits developers and engineers whose Application Integration flows or Integration Connectors tasks fail or stall in production or staging, especially teams that want a repeatable, read-first investigation. It is not the right choice for initial setup, building or publishing integrations, or for workflow tools outside Google Cloud.

Download the skill