env-manager

Generate and validate .env.local and .env.example templates for taw-kit projects.

32|13|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/nghiahsgs/taw-kit --skill env-manager-nghiahsgs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-manager
Source: https://github.com/nghiahsgs/taw-kit/tree/main/skills/env-manager
Command: npx skills add https://github.com/nghiahsgs/taw-kit --skill env-manager-nghiahsgs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Generate and validate .env.local and .env.example templates for taw-kit projects, ensuring required keys exist before builds and deployments, while never logging sensitive values.

Core Features & Use Cases

  • Generate .env.local templates with placeholders for quick local development.
  • Produce .env.example files with safe non-sensitive placeholders to share with teams.
  • Validate presence of required keys before deploy to catch misconfigurations early.

Quick Start

Run env-manager during project init to generate and validate .env.local and .env.example with safe placeholders.

Frequently Asked Questions about env-manager

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

FAQPage Schema
How do I validate environment variables before deploying my project?

To validate environment variables before deploy, run env-manager during project initialization to enforce key presence checks and ensure all required secrets exist in .env.local and .env.example templates.

How do I generate safe .env templates for local development?

Generate safe .env templates by running env-manager at project init, which produces .env.local files with placeholders for quick local setup and .env.example files with non-sensitive values for team sharing.

What is the best way to prevent secret leaks in .env files during CI?

The best way to prevent secret leaks in .env files during CI is to use env-manager for safe placeholder handling and integrate its validation checks to ensure sensitive values are never logged.

Why does my deployment fail due to missing environment configuration?

Deployment fails due to missing environment configuration when required keys are absent; env-manager catches these misconfigurations early by validating the presence of all necessary secrets before the build process.

Can I use env-manager with my existing taw-kit project initialization?

Yes, you can use env-manager with existing taw-kit projects at initialization to generate required .env.local and .env.example templates and validate that all necessary environment keys are present.

What are the limitations of using placeholder values in .env.example files?

The limitation of using placeholder values in .env.example files is that they are non-sensitive substitutes, meaning developers must still manually input actual secret values into .env.local for the application to run correctly.