사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/infisical/ai-skills --skill infisical-setup시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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:
- Local development — They want secrets injected into their dev workflow (CLI)
- Docker — They want secrets in their containers at build time or runtime
- CI/CD — They want secrets in GitHub Actions, GitLab CI, or other pipelines
- Kubernetes — They want the Infisical Operator syncing secrets to K8s
- Application code — They want to fetch secrets programmatically via an SDK
- 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-sdkbut yourequire "infisical"and the class isInfisical::Client. Readreferences/sdks.mdrather 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.