dotenvx

Encrypt and load .env files for multi-environment workflows.

320|3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/mizchi/skills --skill dotenvx-mizchi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotenvx
Source: https://github.com/mizchi/skills/tree/main/tooling/dotenvx
Command: npx skills add https://github.com/mizchi/skills --skill dotenvx-mizchi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Managing environment configurations across multiple environments can be error-prone and expose secrets. dotenvx provides encryption and a consistent runtime to load and apply env vars safely.

Core Features & Use Cases

  • Encrypt and decrypt .env files to protect secrets in source control and CI environments.
  • Load multiple environment files and merge them deterministically for predictable configurations.
  • Integrate with GitHub Actions to securely reference secrets during builds and deployments.

Quick Start

Install dotenvx and encrypt your .env files, then run your application with dotenvx run to load the secrets.

Frequently Asked Questions about dotenvx

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

FAQPage Schema
How do I securely manage environment variables across multiple deployment targets?

To securely manage environment variables across multiple targets, you can encrypt .env files and load them deterministically at runtime, ensuring isolated secrets and reproducible configurations for each environment.

Can I encrypt .env files for safe source control and CI environments?

Yes, you can encrypt .env files to protect secrets within source control and CI environments, decrypting them safely during builds to prevent accidental exposure of sensitive configuration data.

How do I load multiple environment files and merge them for my application?

You can load multiple environment files and merge them deterministically by using a dedicated run command, which composes multi-file configurations to produce predictable application runtime variables.

Does this approach work with GitHub Actions for CI-cd deployments?

Yes, this approach integrates with GitHub Actions to securely reference and decrypt environment secrets during builds and deployments, ensuring reproducible configurations across your CI-CD pipelines.

What is the best way to handle secrets in development without exposing them?

The best way to handle secrets in development without exposing them is applying key encryption and decryption to your local .env files, loading them safely into the application runtime only when needed.

Why do I need encrypted environment variables instead of plain text .env files?

You need encrypted environment variables instead of plain text .env files because managing configurations across multiple environments can be error-prone, and encryption protects secrets from accidental exposure in source control.