What problem does it solve?
This Skill eliminates the critical security risk of plaintext API secrets being accidentally committed to version control, and removes the friction of managing separate, isolated configurations for local, dev, and prod development environments.
Core Features & Use Cases
- Encrypted Secret Storage: All API keys, tokens, and credentials are AES-encrypted in git via dotenvx, with private keys stored off-device in Dotenv Armor to prevent exposure.
- Isolated Environment Profiles: Separate encrypted config files for local, dev, and prod environments, each with its own keypair, so you never accidentally run local code against production backends.
- Automated Guardrails: Pre-commit git hooks auto-encrypt any staged .env files and block commits of unencrypted secrets, while gitleaks and GitHub secret scanning provide additional layers of protection.
- Use Case: When onboarding a new team member, this Skill lets you securely share dev environment secrets without exposing production credentials, and ensures their local setup is configured correctly without manual secret handling.
Quick Start
Use the dotenvx-secrets skill to safely add a new third-party API token to your dev environment without risking exposure in tracked version-controlled files.