Agent skill · software engineering · aiskillstore
env-handler
Manage environment variables securely. Handles distinction between .env (template) and .env.local (secrets).
Why this skill is useful
Provides specific guidelines for managing environment variables securely, which the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Environment Variable Handler Core Rules 1. NO .env.example: Do not create this file. Use .env as the template. 2. Secrets in .env.local: Actual sensitive values must live in .env.local (git-ignored). 3. Placeholders: Every variable in .env.local MUST have a corresponding entry in .env. If sensitive: KEY="" If public/common: KEY="defaultvalue" Instructions 1. Adding a New Sensitive Variable When you need to add a secret (e.g., REPLICATEAPITOKEN): 1. Update .env: Add the variable with an empty string value. 2. Ask the User: Explicitly request the user to add the actual value to their local secrets file. "I have added REPLICATEAPITOKEN to your .env file. Please open .env.local and add the actual token: REPLICATEAPITOKEN=yourtokenhere" 2. Adding a Non-Sensitive Variable When adding a public or configuration variable (e.g., NEXTPUBLICAPPURL): 1. Update .env: Add the variable with its default or development value. 3. Reading Variables Server-side: process.env.KEY Client-side: process.env.NEXTPUBLICKEY Checklist [ ] Is the variable in .env? [ ] If sensitive, is the value in .env empty? [ ] Did I ask the user to update .env.local?
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/env-handler