aiskillstore/marketplace / skills/aayushbaniya2006/env-handler
env-handler
VerifiedManage environment variables securely. Handles distinction between .env (template) and .env.local (secrets).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.6 KB |
| reference.md | markdown | 1.3 KB |
| skill-report.json | config | 65.4 KB |
reference.md
View on GitHub# Environment Variables Reference
## Files & Purpose
| File | Git Status | Purpose | Content Style |
|------|------------|---------|---------------|
| `.env` | Committed ✅ | **Template & Defaults** | `KEY=""` (Secrets)<br>`KEY="val"` (Defaults) |
| `.env.local` | Ignored 🚫 | **Secrets & Overrides** | `KEY="sk-123..."`<br>`KEY="override"` |
| `.env.example` | **FORBIDDEN** ❌ | Do not use | N/A |
## Best Practices
### 1. Variable Naming
- **Server Secrets**: `UPPER_CASE` (e.g., `STRIPE_SECRET_KEY`)
- **Public/Client**: Prefix with `NEXT_PUBLIC_` (e.g., `NEXT_PUBLIC_STRIPE_KEY`)
### 2. Security
- Never commit real API keys to `.env`.
- If you accidentally commit a key, rotate it immediately.
### 3. Deployment (Vercel)
- In production (Vercel), variables from `.env.local` must be added to the **Project Settings > Environment Variables**.
- Variables in `.env` are automatically picked up if the file is committed, but usually, it's better to define them in Vercel for consistency.
## Example
**Local Development:**
`.env`:
```bash
# Database
DATABASE_URL=""
# Auth
NEXTAUTH_SECRET=""
NEXTAUTH_URL="http://localhost:3000"
# Feature Flags
NEXT_PUBLIC_ENABLE_AI="true"
```
`.env.local`:
```bash
# Secrets
DATABASE_URL="postgresql://user:pass@localhost:5432/db"
NEXTAUTH_SECRET="super-secret-hash"
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |