multiAI Summary Pending

env-handler

Manage environment variables securely. Handles distinction between .env (template) and .env.local (secrets).

231 stars

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/env-handler/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/aayushbaniya2006/env-handler/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/env-handler/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How env-handler Compares

Feature / Agent	env-handler	Standard Approach
Platform Support	multi	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Manage environment variables securely. Handles distinction between .env (template) and .env.local (secrets).

Which AI agents support this skill?

This skill is compatible with multi.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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="default_value"`

## Instructions

### 1. Adding a New Sensitive Variable
When you need to add a secret (e.g., `REPLICATE_API_TOKEN`):

1.  **Update `.env`**:
    Add the variable with an empty string value.
    ```bash
    # .env
    REPLICATE_API_TOKEN=""
    ```

2.  **Ask the User**:
    Explicitly request the user to add the actual value to their local secrets file.
    > "I have added `REPLICATE_API_TOKEN` to your `.env` file. Please open `.env.local` and add the actual token: `REPLICATE_API_TOKEN=your_token_here`"

### 2. Adding a Non-Sensitive Variable
When adding a public or configuration variable (e.g., `NEXT_PUBLIC_APP_URL`):

1.  **Update `.env`**:
    Add the variable with its default or development value.
    ```bash
    # .env
    NEXT_PUBLIC_APP_URL="http://localhost:3000"
    ```

### 3. Reading Variables
-   Server-side: `process.env.KEY`
-   Client-side: `process.env.NEXT_PUBLIC_KEY`

## Checklist
- [ ] Is the variable in `.env`?
- [ ] If sensitive, is the value in `.env` empty?
- [ ] Did I ask the user to update `.env.local`?