Terminal
Terminal/Skill
Covers Infisical KMS, where keys stay on the platform and you send data in to encrypt, decrypt, sign, verify or generate HMACs.
By Infisical
Works with
npx skills add infisical/ai-skills --skill infisical-kmsYou 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.
The distinction is what you are protecting:
| If the user wants... | Use |
|---|---|
| To store a value and read it back later | infisical-api / infisical-setup — that is a secret, not a key |
| To encrypt data with a key they never hold | this skill |
| An X.509 certificate for TLS | infisical-pki |
| To sign software artifacts with an audit trail and approvals | infisical-pki — Code Signing |
| A short-lived database credential | infisical-dynamic-secrets |
| To rotate an existing third-party credential | infisical-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.
Every KMS key has exactly one keyUsage, fixed at creation:
keyUsage | For | Operations |
|---|---|---|
encrypt-decrypt | Protecting data | encrypt, decrypt |
sign-verify | Proving authenticity | sign, verify |
generate-verify-mac | Message integrity with a shared key | generate-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.
keyUsage| File | When to read |
|---|---|
references/keys-and-operations.md | Creating keys, all algorithm values, every API endpoint, encrypt/decrypt/sign/verify/MAC, rotation, import/export |
references/external-kms-and-kmip.md | Backing Infisical with AWS KMS or GCP KMS, HSM root keys, KMIP servers, Kubernetes encryption-at-rest, Sigstore cosign |
aes-256-gcm); KMS asymmetric and signing algorithms are UPPER_SNAKE (ECC_NIST_P256, RSASSA_PSS_SHA_256); KMS post-quantum uses underscores (ML_DSA_65) while PKI uses hyphens (ML-DSA-65). Do not carry a value across from infisical-pki.isExportable when there is a concrete requirement, and say plainly that it weakens the guarantee.