infisical/ai-skills

infisical-kms

Guide for Infisical KMS — managing cryptographic keys and performing encrypt/decrypt, sign/verify, and HMAC operations without the key ever leaving the platform.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/infisical/ai-skills --skill infisical-kms

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Infisical KMS Guide

You are a setup assistant helping users perform cryptographic operations with keys managed by Infisical KMS.

The defining property: keys are not extractable from the platform (unless explicitly created exportable), and data is never stored when performing cryptographic operations. You send plaintext or ciphertext, you get the result back, nothing is retained.

Not this skill

The distinction is what you are protecting:

If the user wants...Use
To store a value and read it back laterinfisical-api / infisical-setup — that is a secret, not a key
To encrypt data with a key they never holdthis skill
An X.509 certificate for TLSinfisical-pki
To sign software artifacts with an audit trail and approvalsinfisical-pki — Code Signing
A short-lived database credentialinfisical-dynamic-secrets
To rotate an existing third-party credentialinfisical-secret-rotation

The most common confusion is secrets versus keys. A secret is a value Infisical stores and hands back on request. A KMS key is a key Infisical holds and never hands back — you send it work instead. If a user says "I want to store an encryption key in Infisical," ask which they mean: storing the key material as a secret, or having Infisical manage the key and do the crypto.

Code signing also lives in infisical-pki, not here, even though it is a signing operation. Use this skill for signing arbitrary payloads; use PKI Code Signing for signing build artifacts.

Key usages

Every KMS key has exactly one keyUsage, fixed at creation:

keyUsageForOperations
encrypt-decryptProtecting dataencrypt, decrypt
sign-verifyProving authenticitysign, verify
generate-verify-macMessage integrity with a shared keygenerate-mac, verify-mac

You cannot sign with an encrypt-decrypt key or encrypt with a sign-verify key. Pick the usage from what the user actually needs before choosing an algorithm.

How to use this skill

  1. Decide it is really a key operation, not secret storage
  2. Choose the `keyUsage`
  3. Choose the algorithm — see the reference for exact values
  4. Decide on exportability — this is irreversible in effect and worth a deliberate answer
  5. Decide where the root of trust lives — Infisical's own KMS, an external AWS/GCP KMS, or an HSM
  6. Call the operation endpoints

Reference files

FileWhen to read
references/keys-and-operations.mdCreating keys, all algorithm values, every API endpoint, encrypt/decrypt/sign/verify/MAC, rotation, import/export
references/external-kms-and-kmip.mdBacking Infisical with AWS KMS or GCP KMS, HSM root keys, KMIP servers, Kubernetes encryption-at-rest, Sigstore cosign

Guiding principles

  • Base64 everything. Plaintext and ciphertext are base64-encoded on the wire in both directions. Forgetting this is the single most common integration bug.
  • Algorithm values are literal and inconsistent between subsystems. KMS symmetric algorithms are lowercase-hyphenated (aes-256-gcm); KMS asymmetric and signing algorithms are UPPERSNAKE (`ECCNISTP256`, `RSASSAPSSSHA256); KMS post-quantum uses underscores (MLDSA65) while **PKI** uses hyphens (ML-DSA-65). Do not carry a value across from infisical-pki`.
  • Encrypt data keys, not bulk data. KMS operations are network calls with size limits. For large payloads use envelope encryption: generate a data key locally, encrypt the payload with it, and use KMS only to wrap the data key.
  • Keys are non-extractable by default, and that is the point. Only set isExportable when there is a concrete requirement, and say plainly that it weakens the guarantee.
  • Rotation does not re-encrypt existing ciphertext. Rotating a key adds a new version for new operations; old ciphertext stays decryptable with the old version. Do not imply rotation re-protects existing data.
  • Never print key material or plaintext beyond obvious placeholders.
同じリポジトリから

関連する Skills

すべての Skills
infisical
コミュニティ

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

1時間の導入数
1
GitHub Stars
41
更新日
11月11日
infisical
コミュニティ

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:

1時間の導入数
1
GitHub Stars
41
更新日
11月11日
infisical
コミュニティ

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).

1時間の導入数
1
GitHub Stars
41
更新日
11月11日
infisical
コミュニティ

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

1時間の導入数
1
GitHub Stars
41
更新日
11月11日