dotenvx-secrets

Encrypt API secrets with AES and manage isolated environment keypairs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jbreel77888/Agent-AiNorx --skill dotenvx-secrets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotenvx-secrets
Source: https://github.com/jbreel77888/Agent-AiNorx/tree/main/.claude/skills/dotenvx-secrets
Command: npx skills add https://github.com/jbreel77888/Agent-AiNorx --skill dotenvx-secrets

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about dotenvx-secrets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent plaintext API secrets from being committed to git?

To prevent plaintext secrets from entering version control, this Skill uses pre-commit git hooks to auto-encrypt staged .env files and block unencrypted credentials. It enforces AES encryption on all sensitive API keys before they are committed.

What is the best way to manage isolated environment configs for local, dev, and prod?

Managing isolated environment configs is done by maintaining separate encrypted files for local, dev, and prod environments. Each environment uses its own AES keypair so local code never accidentally runs against production backends or credentials.

How does encrypted secret storage work with dotenvx for development environments?

Encrypted secret storage with dotenvx works by applying AES encryption to credentials in git, while private keys are stored off-device in Dotenv Armor. This prevents exposure while allowing standardized commands for secret rotation and environment switching.

Can I securely share dev environment secrets when onboarding a new team member?

You can securely share dev environment secrets during team member onboarding without exposing production credentials. The Skill isolates environments with separate keypairs and stores private keys off-device to ensure safe configuration setup.

Do I need Dotenv Armor to store private keys off-device?

Dotenv Armor is used to store private keys off-device, preventing direct exposure on local machines. Integrating with it provides an additional layer of security by keeping the decryption keys separate from the encrypted .env files in version control.

Why should I use pre-commit git hooks for environment config management?

Pre-commit git hooks are used for environment config management to enforce automated guardrails that auto-encrypt staged .env files. They block commits of unencrypted secrets and work alongside gitleaks and GitHub secret scanning for layered protection.