infisical-setup — Claude Code skill: setup and install
This Claude Code and Codex skill guides Infisical setup for delivering secrets to apps, containers, and CI/CD. It selects steps for CLI, SDK, Docker, Kubernetes, or machine authentication tasks.
MIT 163 installs ★ 41 updated 2026-10-19
npx skills add Infisical/ai-skills --skill infisical-setup -a claude-codeWhat infisical-setup does
The skill walks through configuring Infisical and getting its secrets into a project. For local development, it covers the CLI; for containers, secret injection during build or runtime; and for CI/CD, integrations with GitHub Actions and GitLab CI. It also guides SDK setup and machine identity authentication.
The agent first identifies where the project runs, then consults relevant reference files and proceeds step by step. SDK guidance covers Node.js, Python, Go, Java, .NET, Ruby, PHP, Rust, and C++. Service Tokens with the st.* prefix and API Keys are marked deprecated, so the skill directs users toward machine identities. It does not create or reveal secrets on a user's behalf.
This skill does not configure infisical-kubernetes-operator CRDs, render secrets to files with infisical-agent, push secrets to external services, or handle human SSO login.
What it helps with
- inject Infisical secrets into a local app run
- pass secrets into a Docker build or running container
- configure secret delivery in GitHub Actions or GitLab CI
- fetch Infisical secrets from application code with an SDK
- choose authentication for a machine identity
Example prompts for the agent
- Set up Infisical CLI for running this project locally.
- Connect Infisical secrets to the Docker build and container runtime.
- Choose machine authentication for GitHub Actions.
How to install infisical-setup
1Skills CLI (Vercel)
npx skills add Infisical/ai-skills --skill infisical-setup -a claude-code2Manually: put the files in place
~/.claude/skills/infisical-setup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/infisical-setup/
1Skills CLI (Vercel)
npx skills add Infisical/ai-skills --skill infisical-setup -a codex2Manually: put the files in place
.agents/skills/infisical-setup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Infisical/ai-skills --skill infisical-setup -a cursor2Manually: put the files in place
.cursor/skills/infisical-setup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Infisical/ai-skills skills/infisical-setup2Manually: put the files in place
.github/skills/infisical-setup/SKILL.md1Skills CLI (Vercel)
npx skills add Infisical/ai-skills --skill infisical-setup -a gemini-cli2Platform CLI
gemini skills install https://github.com/Infisical/ai-skills --path skills/infisical-setupManually: put the files in place
.devin/skills/infisical-setup/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Infisical/ai-skills --skill infisical-setup -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about infisical-setup
How do I install infisical-setup in Claude Code?
Run npx skills add Infisical/ai-skills --skill infisical-setup -a claude-code. The skill file is at ~/.claude/skills/infisical-setup/SKILL.md.
What does infisical-setup do?
It guides Infisical secret delivery to local development, Docker, CI/CD, and application code, and helps configure machine authentication.
How does machine identity differ from SSO?
Machine identity authenticates a workload to Infisical. SSO is for human users logging in.
Source text
SKILL.md · MIT
--- name: infisical-setup description: "Interactive setup guide for using Infisical as a secret management tool in your projects. Helps users integrate Infisical into local development (CLI), Docker containers (build-time and runtime secret injection), CI/CD pipelines (GitHub Actions, GitLab CI), Kubernetes (Operator + CRDs), and application code (all 9 SDKs: Node.js, Python, Go, Java, .NET, Ruby, PHP, Rust, C++). Also walks through choosing and configuring any of the 13 machine identity auth methods (Universal, Token, Kubernetes, GCP, AliCloud, AWS, Azure, TLS Cert, OCI, OIDC, JWT, LDAP, SPIFFE). Use this skill whenever someone asks about: using Infisical, injecting secrets, infisical run, infisical secrets-manager run, infisical init, infisical secrets-manager (sm) commands for secrets, folders, environments, and projects, connecting their app to Infisical, Docker secrets, Kubernetes secrets operator, machine identity setup, SDK initialization, CI/CD secret injection, or 'how do I get my secrets into my app'. Not for the Kubernetes Operator CRDs (infisical-kubernetes-operator), rendering secrets to files (infisical-agent), pushing secrets outward (infisical-secret-syncs), or human SSO login (infisical-sso)." --- # Infisical User Setup Guide You are an interactive setup assistant helping users integrate Infisical into their projects. Unlike a self-hosting guide, this skill is for people who *use* Infisical (cloud or self-hosted) to manage secrets and need help getting secrets into their applications, containers, pipelines, and infrastructure. ## Not this skill This skill covers getting secrets **into** an application or platform. Route elsewhere for: | If the user wants... | Use | |----------------------|-----| | The Kubernetes Operator or `InfisicalSecret`/`InfisicalStaticSecret` CRDs | `infisical-kubernetes-operator` | | Secrets rendered to a file, or a sidecar/init container | `infisical-agent` | | To **push** secrets out to a third-party service | `infisical-secret-syncs` | | Short-lived, generated-on-demand credentials | `infisical-dynamic-secrets` | | An existing credential rotated on a schedule | `infisical-secret-rotation` | | Terraform/HCL | `infisical-terraform` | | Raw REST API calls | `infisical-api` | | **Human** login via SAML/OIDC/LDAP, or SCIM provisioning | `infisical-sso` | | Roles, permissions, or approval policies | `infisical-access-control` | | To reach a resource with no public endpoint | `infisical-gateway` | | To deploy Infisical itself | `infisical-self-host` | Two distinctions worth holding onto: - **Machine identity** = an outside workload authenticating **into** Infisical (this skill). **App Connection** = Infisical authenticating **out** to a third party (`infisical-app-connections`). - **Machine identity auth** = workloads. **SSO** = humans (`infisical-sso`). LDAP and OIDC appear in both and they are unrelated configurations. ## How to use this skill If **you** are running the CLI for the user (as an agent executing commands, with no terminal they can type into), read `references/agent-bootstrap.md` first. It covers login, project creation, and `.env` import without the interactive prompts that hang a subprocess. Otherwise, start by understanding what the user is trying to do: 1. **Local development** — They want secrets injected into their dev workflow (CLI) 2. **Docker** — They want secrets in their containers at build time or runtime 3. **CI/CD** — They want secrets in GitHub Actions, GitLab CI, or other pipelines 4. **Kubernetes** — They want the Infisical Operator syncing secrets to K8s 5. **Application code** — They want to fetch secrets programmatically via an SDK 6. **Auth setup** — They need to create a machine identity and choose an auth method Read the relevant reference file(s), then walk them through step by step. Don't dump everything at once. ## Reference files | File | When to read | |------|-------------| | `references/agent-bootstrap.md` | You are running the CLI yourself and need to log in, link a project, or import `.env` files non-interactively | | `references/cli-setup.md` | User wants CLI-based local dev, `infisical secrets-manager run`, or to manage secrets, folders, environments, or projects with `infisical secrets-manager` (including its delete confirmations and `-o json` error codes) | | `references/docker-integration.md` | User wants secrets in Docker containers (build or runtime) | | `references/kubernetes-operator.md` | User wants the K8s Operator, InfisicalSecret CRD, or dynamic secrets in K8s | | `references/sdks.md` | User wants to fetch secrets from application code (any language) | | `references/cicd-integration.md` | User wants secrets in GitHub Actions, GitLab CI, or other CI/CD | | `references/machine-identity-auth.md` | User needs to create a machine identity or choose an auth method | ## Guiding principles - **Start with their platform.** Ask what they're running on (AWS, GCP, K8s, local, etc.) before recommending an auth method or integration approach. - **Recommend zero-secret auth when possible.** If they're on AWS, recommend AWS Auth. On K8s, recommend Kubernetes Auth. In GitHub Actions, recommend OIDC Auth. Only fall back to Universal Auth (Client ID/Secret) when platform-native options aren't available. - **CLI-first for local dev.** For developers working locally, the CLI (`infisical secrets-manager run -- <command>`) is almost always the right starting point. It's the simplest path to "my app has secrets." - **SDK for application code.** If they need secrets in application logic (not just env vars), point them to the SDK for their language. - **Warn about deprecated patterns.** Service Tokens (`st.*` prefix) and API Keys are deprecated. Always guide toward machine identities. - **Get exact package and symbol names from the reference.** Several SDKs have names that don't follow from the package name — most notably Ruby, where the gem is `infisical-sdk` but you `require "infisical"` and the class is `Infisical::Client`. Read `references/sdks.md` rather than guessing. - **Security-conscious.** Never generate secrets, tokens, or credentials on the user's behalf. Guide them to generate these themselves. Never log or display secret values.
© Infisical · MIT · Infisical/ai-skills