Skip to main content
skill CX Codex

infisical-app-connections — Claude Code skill

infisical-app-connections — an agent skill for wiring Infisical to third-party services: pick the App Connection type, choose an auth method, and hand its ID to syncs or rotations.

MIT 257 installs ★ 41 updated 2026-10-19

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Infisical/ai-skills --skill infisical-app-connections -a claude-code
Open on GitHub

What infisical-app-connections does

The skill walks through App Connection setup: one stored credential that Secret Syncs, rotations, PKI and secret scanning later point to by ID. The consuming feature fixes the type. Rotating a PostgreSQL password needs a postgres connection, and a generic one will not do. The agent asks what you are wiring up, then picks the type and the auth method.

Reference files cover 83 connection types with exact method strings and credentials fields, plus flags for Gateway, platform-managed credentials and rotation. Two of those files are generated from the Infisical source by tools/generate-app-connection-refs.py. Where a secretless option exists, the skill points to it: assume-role over access-key, GitHub App over a PAT.

Gateway routing is narrow. Only 16 connection types accept gatewayId; pass it to any other and validation fails. gatewayId and gatewayPoolId cannot be combined. Resource discovery is the other trap: of 94 endpoints that list provider resources, 88 take a user session only, so a machine identity token gets rejected and you fetch the ID another way.

What it helps with

  • create an AWS App Connection with assume-role
  • work out which connection type a secret sync needs
  • debug a connection not found error while building a sync
  • route a connection through a Gateway into a private network
  • reuse one connection across several syncs

Example prompts for the agent

  • I want Infisical to push secrets to AWS. Which App Connection type should I create, and how?
  • Creating a sync fails with connection not found — what should I check?
  • Our database sits on a private network. How do I attach a Gateway to the connection?

How to install infisical-app-connections

1Skills CLI (Vercel)

npx skills add Infisical/ai-skills --skill infisical-app-connections -a claude-code

2Manually: put the files in place

~/.claude/skills/infisical-app-connections/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/infisical-app-connections/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about infisical-app-connections

How do I install infisical-app-connections in Claude Code?

Run npx skills add Infisical/ai-skills --skill infisical-app-connections -a claude-code. The skill lands in ~/.claude/skills/infisical-app-connections/SKILL.md.

What does infisical-app-connections do?

It guides an agent through creating an App Connection, the link between an Infisical organization and an outside service that syncs, rotations, PKI and scanning reference by ID. It also settles which connection type and auth method apply.

How is an App Connection different from a machine identity?

A machine identity lets an outside workload authenticate into Infisical. An App Connection goes the other way: Infisical authenticates out to a third party. Holding a Client ID and Client Secret issued by Infisical means you want infisical-setup instead.

Source text

SKILL.md · MIT
---
name: infisical-app-connections
description: "Guide for creating and managing Infisical App Connections — the reusable authenticated links between Infisical and third-party services that Secret Syncs, Secret Rotations, PKI certificate authorities, PKI Syncs, and Secret Scanning data sources all depend on. Covers all 83 connection types and their exact auth methods (AWS assume-role vs access-key, GitHub OAuth vs GitHub App vs PAT, Azure OAuth vs client-secret vs certificate, GCP service account impersonation, and more), platform-managed credentials, Gateway-routed connections for private networks, and connection-level credential rotation. Use this skill when someone asks about: App Connections, connecting Infisical to AWS/GCP/Azure/GitHub, 'connection not found' when creating a sync, which auth method a connection needs, reusing a connection across syncs, or 'how do I authenticate Infisical to a third-party service'. This is Infisical authenticating OUTWARD to a third party. Not for machine identities, which are workloads authenticating INTO Infisical (infisical-setup)."
---
# Infisical App Connections Guide

You are a setup assistant helping users create App Connections — the reusable, authenticated
connection between an Infisical organization and a third-party service.

An App Connection holds credentials once and is then referenced by ID from many features. It is a
**prerequisite**, not a feature in its own right: users usually arrive here because something else
demanded a `connectionId`.

## Why this is its own skill

Five different features consume App Connections:

| Feature | Skill | What it uses the connection for |
|---------|-------|--------------------------------|
| Secret Syncs | `infisical-secret-syncs` | Pushing secrets to the destination |
| Secret Rotations | `infisical-secret-rotation` | Changing the credential at the source |
| PKI Syncs | `infisical-pki` | Pushing certificates to a destination |
| Certificate Authorities | `infisical-pki` | ACME DNS validation, ADCS, Venafi, DigiCert |
| Secret Scanning data sources | `infisical-secret-scanning` | Reading repositories to scan |

The connection type is **fixed by the consuming feature**. A PostgreSQL secret rotation requires a
`postgres` connection specifically; you cannot substitute a generic one. Always confirm which
connection type the target feature demands before creating one.

## Not this skill

| If the user wants... | Use |
|----------------------|-----|
| To push secrets to a service | `infisical-secret-syncs` (create the connection here first) |
| To rotate an existing credential | `infisical-secret-rotation` |
| A machine identity so *their workload* can authenticate **to** Infisical | `infisical-setup` — that is the opposite direction |
| To reach a private network | `infisical-gateway` — then attach the gateway to a connection here |

The direction of trust is the thing people confuse. A **machine identity** lets an outside workload
authenticate *into* Infisical. An **App Connection** lets Infisical authenticate *out* to a third
party. If the user is holding a Client ID and Client Secret that Infisical issued, they want
machine identities, not this skill.

## How to use this skill

1. **Find out which feature needs it** and therefore which connection type is required
2. **Pick the auth method** — most connections support several, with meaningfully different setup
3. **Grant the minimum permissions** on the third-party side
4. **Decide on Gateway routing** if the target is not publicly reachable
5. **Create the connection**, then reference its UUID from the consuming feature

## Reference files

Two of these are **generated from the Infisical source** — they hold facts, and
`tools/generate-app-connection-refs.py` reproduces them. The rest are hand-written guidance.

| File | Generated? | When to read |
|------|-----------|-------------|
| `references/api-surface.md` | **yes** | The endpoints: per-connection CRUD, and which discovery endpoints a machine identity can actually call |
| `references/credentials-by-connection.md` | **yes** | Exact `method` values and `credentials` fields for all 83 connections |
| `references/connection-catalog.md` | no | The 83 connections at a glance, with Gateway / platform-managed / rotation capability flags |
| `references/cloud-providers.md` | no | AWS, GCP, Azure (all variants), and their permission requirements |
| `references/git-and-cicd.md` | no | GitHub (+ GitHub Radar), GitLab, Bitbucket, Azure DevOps, CI providers |
| `references/databases-and-infra.md` | no | PostgreSQL, MySQL, MSSQL, OracleDB, MongoDB, Redis, LDAP, SSH, SMB/WinRM, and Gateway + platform-managed credentials |

## Guiding principles

- **Prefer the zero-secret method where one exists.** AWS `assume-role` beats `access-key`. GCP only offers `service-account-impersonation`. GitHub App beats a PAT. Only fall back to a static credential when the platform gives no alternative.
- **Auth method values are exact strings.** `assume-role`, `access-key`, `github-app`, `pat`, `client-secret`, `service-account-impersonation`. Read them from the catalog rather than guessing; near-misses like `access-keys` or `github_app` fail validation.
- **One connection, many consumers.** Connections are org-level and reusable. Do not create one per sync. Optionally scope one to a project with `projectId`.
- **A connection is not a Gateway.** Only 16 connection types accept `gatewayId`. For the rest, passing one is a validation error, not a no-op.
- **`gatewayId` and `gatewayPoolId` are mutually exclusive.** Specifying both fails.
- **Connection credential rotation is a different feature from Secret Rotation.** Five connection types can rotate *their own* stored credential. That does not write anything into your secrets — for that, use `infisical-secret-rotation`.
- **Most resource-discovery endpoints cannot be automated.** Infisical exposes 94 endpoints that list a provider's resources (vaults, repositories, clusters). **88 are `AuthMode.JWT` only** — a user session. A machine identity access token is rejected, and many are marked in-source as "not exposed and for Infisical App use". Only 6 accept a machine identity token. To get a resource ID for a sync or rotation config, query the provider directly, or create the resource once in the UI and read its config back through the API. See `references/api-surface.md`.
- **Resolve a connection by name, not by UUID.** `GET /api/v1/app-connections/<slug>/connection-name/{connectionName}` exists and accepts a machine identity token, so automation need not store UUIDs.
- **Least privilege on the third-party side.** The connection's permissions bound what every consuming sync and rotation can do. Scope narrowly, and mention this when a user is about to hand over an admin key.
- **Never generate credentials on the user's behalf,** and never echo a credential back.

© Infisical · MIT · Infisical/ai-skills

Similar skills

All skills for Security →

From the same set17

The whole set →
infisical-dynamic-secrets infisical-dynamic-secrets guides the configuration of on-demand, ephemeral credentials across 30 Infisical providers. Useful when CI pipelines or developers need temporary database or cloud access. CX Codex +1 852installs infisical-self-host infisical-self-host guides self-hosted deployments of the Infisical platform using Docker, Compose, or Kubernetes. Useful for configuring required PostgreSQL, Redis, and encryption variables. CX Codex +1 834installs infisical-terraform Walks your agent through the Infisical Terraform provider: provider auth, ephemeral secrets that stay out of state, and OIDC for Terraform Cloud. CX Codex +1 586installs infisical-access-control A reference skill for Infisical access control: roles, narrow secret permissions, time-bound access, approval policies and audit log streaming. CX Codex +1 267installs infisical-secret-rotation infisical-secret-rotation guides the setup of periodic credential replacement across 28 providers, writing updated values directly back to Infisical. CX Codex +1 255installs infisical-secret-scanning Sets an agent up with Infisical Secret Scanning: repo data sources, the infisical scan CLI, pre-commit hooks and tuning to cut noise. CX Codex +1 254installs infisical-kms A guide that walks the agent through Infisical KMS: encrypt, decrypt, sign, verify and HMAC with keys that never leave the platform. CX Codex +1 238installs infisical-pam Guides setup for brokering human and AI agent infrastructure access via Infisical PAM without revealing credentials. CX Codex +1 238installs

Project sponsors

Companies that keep this analytics open