skills.rest
alisonbessa
alisonbessaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

env-handler

Manage environment variables by separating .env templates from .env.local secrets.

Updated Aug 23, 2026
Search Tags:#devops#security#configuration#secrets#env#dotenv
One-click install
npx skills add https://github.com/alisonbessa/bluemoon --skill env-handler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: env-handler
Source: https://github.com/alisonbessa/bluemoon/tree/main/.claude/skills/env-handler
Command: npx skills add https://github.com/alisonbessa/bluemoon --skill env-handler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage environment variables securely by distinguishing templates (.env) from secrets (.env.local) and enforcing a safe, auditable workflow.

Core Features & Use Cases

  • Enforces using .env as the template and forbids .env.example
  • Keeps secrets in .env.local (git-ignored) with explicit user prompts
  • Requires every key in .env.local to have a corresponding entry in .env

Quick Start

Add placeholder keys to .env and their actual values to .env.local, ensuring every .env.local key has a corresponding entry in .env.

Frequently Asked Questions about env-handler

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

FAQPage Schema
How do I securely manage environment variables for local development and deployment?▼

Securely manage environment variables by separating template keys in .env from actual secret values in .env.local, enforcing an auditable workflow where placeholders and secrets are kept distinct across local development and deployment.

What is the difference between .env and .env.local for secrets?▼

The difference between .env and .env.local is that .env holds placeholder template keys while .env.local stores actual secret values, keeping secrets git-ignored and requiring a one-to-one key mapping between both files.

How do I set up dotenv templates and secrets for deployment?▼

Set up dotenv templates and secrets by adding placeholder keys to .env and their corresponding actual values to .env.local, ensuring every key in .env.local has a matching entry in the .env template file.

Can I use .env.example instead of .env for environment variable templates?▼

You cannot use .env.example for environment variable templates because this workflow explicitly forbids .env.example and enforces using .env as the standard template file to maintain a safe, auditable configuration workflow.

Why does my .env.local configuration require a matching .env template?▼

Your .env.local configuration requires a matching .env template because the system enforces a one-to-one mapping between keys, ensuring every secret in .env.local has a declared placeholder in .env for safe management.

What are the limitations of separating secrets into .env.local files?▼

Limitations of separating secrets into .env.local files include the strict requirement for .env presence and a one-to-one key mapping with .env.local, meaning any missing template placeholder will break the configuration workflow.

Related Skills

Explore More Software Engineering Skills→
iamladiiamladi
1

check-env-keys

Compare environment variable keys across .env files and shell against templates.

Community
Intermediate
PlazaCCPlazaCC
2

dotenvx

Encrypt .env files and inject decrypted variables into process.env at runtime.

Official
Intermediate
shiimanshiiman
2

gitignore-check

Identify missing .gitignore patterns and propose ignore rules before commits.

Community
Intermediate
pulumipulumi
63

pulumi-esc

Manage environments, secrets, and configuration with Pulumi ESC CLI commands.

Official
Intermediate