Guide · Agent skill
How to use the Application Integration Authoring agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The application-integration-authoring skill is a set of instructions that teaches an AI agent how to work with Google Cloud Application Integration, a service for building automated workflows, through its REST API and the Python discovery client. After following this guide you will know how to install the skill, make a request the agent will recognise, and set up the Google Cloud prerequisites it depends on. No prior experience with agent skills is assumed.
Application Integration Authoringgoogle/skills · Apache-2.0 Download the skill Quick start
- 1Download and unzip the skill. Download the ZIP from this page and unzip it. The folder contains SKILL.md and a references folder.
- 2Place it in a skills folder. Move the folder to ~/.claude/skills/ for personal use, or to .claude/skills/ inside your project. Alternatively, upload the ZIP under Settings > Capabilities > Skills.
- 3Prepare Google Cloud. Make sure your project has billing enabled, and enable the Application Integration, Connectors and Secret Manager APIs with gcloud.
- 4Provision your region. Confirm your target region is supported and provisioned for Application Integration before authoring integrations.
- 5Authenticate. Sign in with gcloud, and if you use the Python client, set up application default credentials. Approve these commands when the agent asks.
- 6Make a request. Ask the agent in plain language, naming the region and integration, for example to list integrations or export a version.
- 7Approve changes. Review the exact command and payload the agent shows you, then confirm or decline before any state change runs.
What the skill makes the agent do
Once installed, the agent knows the correct REST endpoints and Python client calls to list, download, upload, publish, test and invoke integrations. It can also move integration versions between environments, for example as part of a CI/CD pipeline that promotes versions from development to staging and production.
The skill tells the agent to ask for your approval before any change, and to avoid storing secrets in plain-text config variables. Read-only actions such as listing integrations and downloading versions run without asking.
- List integrations and their versions in a region
- Download an integration version as JSON for source control
- Upload JSON to create or update a DRAFT version
- Publish, test and invoke integrations
- Promote versions across environments
Install the skill from the ZIP file
Download the ZIP file for the skill from this page and unzip it. Place the resulting folder in one of two locations: your personal skills folder at ~/.claude/skills/, or a project-specific folder at .claude/skills/ inside your project.
Alternatively, you can upload the ZIP in the Claude apps under Settings > Capabilities > Skills.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ in your project folder
- Claude apps: Settings > Capabilities > Skills, then upload the ZIP
Set up Google Cloud before the agent does any work
The skill needs a Google Cloud project with an active billing account attached, even when usage stays within the free tier. It also needs the Google Cloud SDK (gcloud) for authentication, enabling APIs and IAM. Enable the APIs the skill uses with the command below.
Application Integration is regional. The region is the LOCATION in every REST path, and it must be provisioned before you author integrations. If you have no preference, the skill suggests us-central1 as a well-supported default, after you confirm it is listed on the Application Integration locations page. Region provisioning is handled by the separate application-integration-basics skill.
- Google Cloud SDK (gcloud) installed
- Project with billing enabled and the Application Integration API enabled
- A provisioned Application Integration region
- IAM roles such as integrationEditor, integrationDeployer or integrationInvoker
- For the Python client: google-api-python-client and google-auth
gcloud services enable integrations.googleapis.com connectors.googleapis.com secretmanager.googleapis.comTrigger the skill with natural requests
You do not need special syntax. Describe the task in plain language that mentions integrations, versions, JSON, publishing or CI/CD promotion. The skill's description lists these triggers: listing integrations, downloading or uploading integration versions as JSON, configuring API triggers or config variables, publishing drafts, invoking integrations, and automating CI/CD promotion.
If your request is really about first-time project setup, IAM role setup, failed runs or logs, the skill will hand off to application-integration-basics or application-integration-troubleshooting instead.
- Example: List the integrations in us-central1 for my project.
- Example: Download version 3 of the order-sync integration as JSON so I can commit it.
- Example: Upload this JSON as a new DRAFT of the order-sync integration.
- Example: Promote the staging version of order-sync to production.
Review approvals and safety notes
The skill asks for explicit confirmation before creating, uploading, patching, publishing, unpublishing, testing, executing, scheduling or deleting an integration or version, and before changing IAM or auth configs. It shows the exact command and payload first. Host changes also need your approval, including pip install and gcloud config set, and gcloud auth commands.
The skill runs scripts and uses the network, so read the commands it proposes before approving them. Config variables (CONFIG_*) are stored and exported in plain text, so the skill uses authentication profiles or the Secret Manager access task for credentials. Do not paste secrets into config variables yourself.
- Read-only actions run without approval
- State changes and executions need explicit confirmation
- Install and credential changes need your approval
- Use authentication profiles or Secret Manager, not CONFIG_* variables, for secrets
Tips for getting reliable results
Name the region and integration explicitly in your request, because every REST path depends on the LOCATION. When editing a DRAFT, ask the agent to check the lockHolder first, since the skill's guidance is to check it before patching or uploading.
Keep the exported JSON in source control so that changes are reviewed as diffs. Publishing an existing version and uploading a new one need different IAM roles, so check the roles first if a request fails on permissions.
- State the region and integration name in every request
- Check lockHolder before editing a DRAFT
- Store exported JSON in version control and review diffs
- Check IAM roles before publishing or uploading
What people use it for
- Exporting integration versions to a Git repository for code review
- Promoting a tested version from a staging project to production in a CI/CD pipeline
- Uploading an edited JSON file as a new DRAFT and publishing it after approval
- Listing integrations and versions in a region to audit what is deployed
Frequently asked questions
How do I install the application-integration-authoring skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into .claude/skills/ inside a project. You can also upload the ZIP in the Claude apps under Settings > Capabilities > Skills.
What do I need before the skill is useful?
You need a Google Cloud project with billing enabled, the Application Integration API enabled, a provisioned Application Integration region, the Google Cloud SDK for authentication, and suitable IAM roles such as integrationEditor, integrationDeployer or integrationInvoker. The skill does not work well without these.
Is the skill free?
The skill is licensed under Apache-2.0. The source does not state pricing for Google Cloud Application Integration itself, and the prerequisites note that a billing account is required even within the free tier.
Does the skill diagnose failed integration runs?
No. Diagnosing failed or stuck runs, execution logs and quota errors belongs to the separate application-integration-troubleshooting skill. Initial project setup, region provisioning and IAM role setup belong to application-integration-basics.
Will the agent change my integrations without asking?
Not for state changes. The skill requires explicit confirmation before creating, uploading, publishing, testing, executing or deleting integrations or versions, and before host or credential changes. Read-only actions such as listing and downloading run freely.
Are there alternatives to this skill?
The source says there is no gcloud integrations command group, no Google-managed MCP server for Application Integration, and no documented Terraform resource for integrations or versions. Work with the REST API directly or use the Python discovery client, which this skill is built around.
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 teams who manage Google Cloud Application Integration workflows as code and want an agent to export, edit, and promote integration JSON with approval checkpoints. It is not a good fit if you have no Google Cloud project yet, or if your main need is setup, IAM, or diagnosing failed runs, which the companion skills cover.
Download the skill