infisical/ai-skills

infisical-setup

Interactive setup guide for using Infisical as a secret management tool in your projects.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/infisical/ai-skills --skill infisical-setup

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

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 CRDsinfisical-kubernetes-operator
Secrets rendered to a file, or a sidecar/init containerinfisical-agent
To push secrets out to a third-party serviceinfisical-secret-syncs
Short-lived, generated-on-demand credentialsinfisical-dynamic-secrets
An existing credential rotated on a scheduleinfisical-secret-rotation
Terraform/HCLinfisical-terraform
Raw REST API callsinfisical-api
Human login via SAML/OIDC/LDAP, or SCIM provisioninginfisical-sso
Roles, permissions, or approval policiesinfisical-access-control
To reach a resource with no public endpointinfisical-gateway
To deploy Infisical itselfinfisical-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

FileWhen to read
references/agent-bootstrap.mdYou are running the CLI yourself and need to log in, link a project, or import .env files non-interactively
references/cli-setup.mdUser 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.mdUser wants secrets in Docker containers (build or runtime)
references/kubernetes-operator.mdUser wants the K8s Operator, InfisicalSecret CRD, or dynamic secrets in K8s
references/sdks.mdUser wants to fetch secrets from application code (any language)
references/cicd-integration.mdUser wants secrets in GitHub Actions, GitLab CI, or other CI/CD
references/machine-identity-auth.mdUser 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.
del mismo repositorio

Más Skills

Todos los Skills
infisical
Comunidad

infisical-access-control

Guide for Infisical access control and governance — org and project roles, custom roles with subject/action permissions, granular secret permissions that separate describing a secret from reading its value, attribute-based access control (ABAC) driven by user metadata and machine identity attributes, additional privileges, assume-privilege, temporary (time-bound) access, access requests, change-approval and access-approval policies, and audit logs including streaming to Splunk, Datadog, Azure, C

Instalaciones / 1h
1
GitHub Stars
41
Actualizado
11 nov
infisical
Comunidad

infisical-agent

Guide for configuring the Infisical Agent — a client daemon that manages token lifecycle and renders secrets via Go templates without modifying application code. Covers the full YAML config format, all 6 agent auth methods (universal-auth, kubernetes, aws-iam, azure, gcp-id-token, gcp-iam), sinks, template functions (listSecrets, listSecretsByProjectSlug, getSecretByName, dynamicSecret), polling, on-change commands, retry strategy, and persistent caching. Use this skill when someone asks about:

Instalaciones / 1h
1
GitHub Stars
41
Actualizado
11 nov
infisical
Comunidad

infisical-api

Interact with the Infisical REST API to manage secrets, projects, environments, machine identities, and more. Supports secret CRUD operations, machine identity authentication, pagination, and rate limiting on cloud deployments. Not for the CLI/SDKs (infisical-setup), KMS crypto endpoints (infisical-kms), certificate endpoints (infisical-pki), or human SSO login (infisical-sso).

Instalaciones / 1h
1
GitHub Stars
41
Actualizado
11 nov
infisical
Comunidad

infisical-app-connections

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 cred

Instalaciones / 1h
1
GitHub Stars
41
Actualizado
11 nov