smithery.ai

env-setup

Environment configuration and secrets management. Use when setting up .env files, managing secrets, or configuring environments.

First seen Mar 19, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,451 B
  • docs SUMMARY.md 315 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Environment Configuration

Non-Negotiable Rules

Rule Why
NEVER commit .env to git Secrets persist in history forever
NEVER log secret values Logs stored in plain text, forwarded
NEVER hardcode secrets Source code is widely shared
ALWAYS use .env.example Documents vars without exposing values
ALWAYS add .env* to .gitignore FIRST Prevents accidental commit
ALWAYS validate config at startup Fail fast, not hours into production

.gitignore (add before creating .env)

.env
.env.*
!.env.example
*.pem
*.key
credentials.json

Naming Conventions

  • UPPERSNAKECASE: DATABASEURL, JWTSECRET
  • Prefix by service: DB, REDIS, AWS_
  • Booleans: ENABLE_CACHE=true (not 1/yes)
  • Feature flags: FEATURE_*

Key Patterns

  • No defaults for secrets — force explicit configuration
  • Validate at startup with Zod/Joi/Pydantic, not at first use
  • Unique secrets per environment — one leak shouldn't compromise all
  • Rotate leaked secrets immediately — check git history, audit access logs
  • Process env always wins — CI/CD overrides file-based config