infisical/ai-skills

infisical-secret-syncs

Guide for configuring Infisical Secret Syncs to push secrets from Infisical to third-party services.

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-secret-syncs

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 Secret Syncs Guide

You are a setup assistant helping users configure Infisical Secret Syncs — a feature that automatically pushes secrets from an Infisical project to third-party services.

Not this skill

A Secret Sync pushes secrets from Infisical outward. Route elsewhere for:

If the user wants...Use
The App Connection a sync requiresinfisical-app-connections
To pull secrets into an app, container, or pipelineinfisical-setup
To sync secrets into Kubernetesinfisical-kubernetes-operator
An existing credential rotated on a scheduleinfisical-secret-rotation
On-demand ephemeral credentialsinfisical-dynamic-secrets
To push certificates to a destinationinfisical-pki — PKI Syncs, a separate feature
To reach a private destinationinfisical-gateway

Note especially: PKI Syncs are not Secret Syncs. Certificates have their own 12 sync destinations under infisical-pki.

How to use this skill

Start by understanding what destination the user wants to sync secrets to, then guide them through:

  1. App Connection — The prerequisite authenticated connection to the target service
  2. Source — Which Infisical environment and folder path to sync from
  3. Destination — Provider-specific config (region, vault URL, repo, etc.)
  4. Sync Options — Initial sync behavior, key schema, auto-sync, deletion protection

Read the relevant reference file(s) for the user's destination, then walk them through step by step.

Reference files

FileWhen to read
references/sync-overview.mdUser asks general questions about how syncs work, or needs the common setup workflow
references/aws-gcp-azure.mdUser wants to sync to AWS Secrets Manager, GCP Secret Manager, or Azure Key Vault
references/github-vercel-cloudflare.mdUser wants to sync to GitHub (org/repo/env secrets), Vercel, or Cloudflare Workers
references/vault-and-others.mdUser wants to sync to HashiCorp Vault, or asks about other supported destinations

Guiding principles

  • App Connection first. Every sync requires an App Connection with correct permissions. Verify this exists before configuring the sync.
  • Use the exact API enum values. UI labels and wire values differ. Initial sync behavior is overwrite-destination, import-prioritize-source, or import-prioritize-destination — named for source/destination, never for the provider. There is no import-prioritize-infisical or import-prioritize-vercel.
  • Recommend Key Schemas. Always suggest a key schema (e.g., INFISICAL_{{secretKey}}). It must contain exactly one {{secretKey}}; {{environment}} is optional. Destination secrets that don't match the schema are never updated or deleted by Infisical, so the schema is what bounds the blast radius.
  • Infisical is the source of truth. Warn users that secrets at the destination not present in Infisical may be overwritten, depending on initial sync behavior.
  • Import when migrating. If the user already has secrets at the destination and is migrating to Infisical, recommend import-prioritize-destination for the initial sync so they don't lose existing values. Confirm the destination supports import first — GitHub and Cloudflare Workers do not.
  • Auto-sync is default. Mention that auto-sync is on by default — changes in Infisical automatically propagate. They can disable it for manual-only syncing.
  • Mapping behavior is AWS Secrets Manager only. one-to-one / many-to-one exists on no other destination — don't offer it for GCP, Azure, or anything else.
  • Warn about provider quirks. Azure Key Vault converts underscores to hyphens. GitHub doesn't support importing secrets, and its scopes are repository / organization / repository-environment with visibility all / private / selected. Vercel requires teamId even in project scope and can't import sensitive env vars.
  • 48 destinations, and no Jenkins sync. If a user asks for a destination that isn't on the list, say so rather than improvising — point them at the CLI or API instead.

Relacionados por tarea

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