Encrypt and decrypt YAML, JSON, ENV, and INI secrets with SOPS.
npx skills add https://github.com/nq-rdl/agent-extensions --skill sops-nq-rdl
Please help me install this Agent Skill. Skill: sops Source: https://github.com/nq-rdl/agent-extensions/tree/main/skills/sops Command: npx skills add https://github.com/nq-rdl/agent-extensions --skill sops-nq-rdl
Encrypting and decrypting secrets across project files (YAML, JSON, ENV, INI, and binary data) to keep configurations secure while maintaining readable diffs, with flexible backends.
Install the SOPS CLI, configure an Age or Vault transit key, and begin encrypting your secret files.
High-intent search queries and answers about installing and using this skill.
You can encrypt secrets in YAML, JSON, ENV, and INI config files for Git using SOPS with Age or Vault backends. It maintains readable diffs while keeping configurations secure through per-file encryption rules declared in a .sops.yaml file.
Yes, SOPS supports both Age and Vault transit backends for config encryption. These backends allow you to securely manage multiple recipients, perform key rotation, and execute in-place editing of your encrypted files.
The best way to manage shared CI/CD and infrastructure secrets across teams is encrypting them directly in config files with SOPS. It allows per-path encryption rules via .sops.yaml, enabling secure Git-tracked configurations without exposing plaintext.
Yes, you need a .sops.yaml file to declare per-path encryption rules when using SOPS. This file defines which files get encrypted and specifies the Age or Vault transit backend keys required for the encryption and decryption processes.
Yes, SOPS allows you to rotate encryption keys and edit encrypted files in place. This ensures that when keys are compromised or updated, you can re-encrypt your secrets with new keys across all specified configuration files.
Use SOPS instead of full file encryption because it encrypts only the secret values in YAML, JSON, and other files, leaving keys and structure in plaintext. This approach maintains readable Git diffs and prevents accidental plaintext secret exposure.
89jobrienManage encrypted secrets and SSH credentials with age, sops, and 1Password CLI.
mahg-esProvision AWS, OCI, and Hetzner infrastructure with Terraform or Pulumi modules.
jdiegosierraProvides Terraform and GCP users with curated, actionable answersbbaased on official documentation and real-world experience.
Camilo8902Manage environment variables and secrets with encryption, rotation, and provider integration.
