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 |
skill-report.json
View on GitHub{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-07-04T23:49:47.349Z",
"slug": "aayushbaniya2006-env-handler",
"source_url": "https://github.com/AayushBaniya2006/blinkfund/tree/main/.claude/skills/env-handler",
"source_ref": "main",
"model": "codex",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "1666666b89e9507733ee6882edba43e603342e9dca924cb5715691fe529c611f",
"tree_hash": "dd3039a5e8fea93c55d44fe577820be4add3554a7d28e641293149c87bbe2870",
"provenance": {
"model_requested": "gpt-5.5:high",
"model_effective": "codex:gpt-5.5:high",
"fallback_chain": [
{
"agent": "codex",
"model": "gpt-5.5",
"effort": "high",
"outcome": "success"
}
],
"analysis_version": "3.0.0"
}
},
"skill": {
"name": "env-handler",
"description": "Manage environment variable templates and local secret files with clear project conventions.",
"summary": "Guides safe separation of committed .env templates from local secret overrides.",
"icon": "📦",
"version": "1.0.0",
"author": "AayushBaniya2006",
"license": "MIT",
"tags": [
"environment-variables",
"secrets",
"dotenv",
"nextjs",
"vercel"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": [
"network",
"env_access",
"external_commands"
],
"category": "devops"
},
"security_audit": {
"risk_level": "high",
"is_blocked": false,
"safe_to_publish": false,
"analysis_status": "ok",
"summary": "The skill is documentation-only and I found no prompt injection, exfiltration intent, or executable command behavior. The main confirmed risk is legitimate but sensitive environment-file handling around .env and .env.local, which requires strong guardrails before publication.",
"remediation": [
{
"issue": "The skill operates near .env.local, which is intended to contain real secrets.",
"suggestion": "Add an explicit rule to never read, print, summarize, or copy existing .env.local values. Only ask users to enter secret values locally.",
"severity": "high"
},
{
"issue": "The reference uses realistic credential-shaped examples for local secrets.",
"suggestion": "Replace sample database URLs and secret hashes with clearly fake placeholders that cannot be mistaken for usable credentials.",
"severity": "medium"
},
{
"issue": "Environment file edits can accidentally commit sensitive values.",
"suggestion": "Require a final check that committed .env entries for sensitive variables are empty before any commit or deployment step.",
"severity": "high"
}
],
"risk_factor_evidence": [
{
"factor": "network",
"evidence": [
{
"file": "reference.md",
"line_start": 36,
"line_end": 36
},
{
"file": "SKILL.md",
"line_start": 38,
"line_end": 38
}
]
},
{
"factor": "env_access",
"evidence": [
{
"file": "reference.md",
"line_start": 32,
"line_end": 32
},
{
"file": "reference.md",
"line_start": 45,
"line_end": 45
},
{
"file": "reference.md",
"line_start": 14,
"line_end": 14
},
{
"file": "SKILL.md",
"line_start": 42,
"line_end": 42
},
{
"file": "SKILL.md",
"line_start": 43,
"line_end": 43
},
{
"file": "SKILL.md",
"line_start": 42,
"line_end": 42
},
{
"file": "SKILL.md",
"line_start": 43,
"line_end": 43
}
]
},
{
"factor": "external_commands",
"evidence": [
{
"file": "SKILL.md",
"line_start": 9,
"line_end": 9
},
{
"file": "SKILL.md",
"line_start": 10,
"line_end": 10
},
{
"file": "SKILL.md",
"line_start": 11,
"line_end": 11
},
{
"file": "SKILL.md",
"line_start": 12,
"line_end": 12
},
{
"file": "SKILL.md",
"line_start": 13,
"line_end": 13
},
{
"file": "SKILL.md",
"line_start": 18,
"line_end": 18
},
{
"file": "SKILL.md",
"line_start": 20,
"line_end": 20
},
{
"file": "SKILL.md",
"line_start": 22,
"line_end": 25
},
{
"file": "SKILL.md",
"line_start": 25,
"line_end": 29
},
{
"file": "SKILL.md",
"line_start": 29,
"line_end": 29
},
{
"file": "SKILL.md",
"line_start": 32,
"line_end": 34
},
{
"file": "SKILL.md",
"line_start": 34,
"line_end": 36
},
{
"file": "SKILL.md",
"line_start": 36,
"line_end": 39
},
{
"file": "SKILL.md",
"line_start": 39,
"line_end": 42
},
{
"file": "SKILL.md",
"line_start": 42,
"line_end": 43
},
{
"file": "SKILL.md",
"line_start": 43,
"line_end": 46
},
{
"file": "SKILL.md",
"line_start": 46,
"line_end": 47
},
{
"file": "SKILL.md",
"line_start": 47,
"line_end": 48
}
]
}
],
"static_findings": [
{
"id": "network:reference.md:36:hardcoded-url",
"category": "network",
"severity": "low",
"pattern": "Hardcoded URL",
"file": "reference.md",
"line_start": 36,
"line_end": 36,
"snippet": "NEXTAUTH_URL=\"http://localhost:3000\""
},
{
"id": "env_access:reference.md:32:database-connection-strings",
"category": "env_access",
"severity": "high",
"pattern": "Database connection strings",
"file": "reference.md",
"line_start": 32,
"line_end": 32,
"snippet": "DATABASE_URL=\"\""
},
{
"id": "env_access:reference.md:45:database-connection-strings",
"category": "env_access",
"severity": "high",
"pattern": "Database connection strings",
"file": "reference.md",
"line_start": 45,
"line_end": 45,
"snippet": "DATABASE_URL=\"postgresql://user:pass@localhost:5432/db\""
},
{
"id": "env_access:reference.md:14:generic-api-secret-keys",
"category": "env_access",
"severity": "high",
"pattern": "Generic API/secret keys",
"file": "reference.md",
"line_start": 14,
"line_end": 14,
"snippet": "- **Server Secrets**: `UPPER_CASE` (e.g., `STRIPE_SECRET_KEY`)"
},
{
"id": "sensitive:reference.md:7:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "reference.md",
"line_start": 7,
"line_end": 7,
"snippet": "| `.env` | Committed ✅ | **Template & Defaults** | `KEY=\"\"` (Secrets)<br>`KEY=\"val\"` (Defaults) |"
},
{
"id": "sensitive:reference.md:8:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "reference.md",
"line_start": 8,
"line_end": 8,
"snippet": "| `.env.local` | Ignored 🚫 | **Secrets & Overrides** | `KEY=\"sk-123...\"`<br>`KEY=\"override\"` |"
},
{
"id": "sensitive:reference.md:9:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "reference.md",
"line_start": 9,
"line_end": 9,
"snippet": "| `.env.example` | **FORBIDDEN** ❌ | Do not use | N/A |"
},
{
"id": "sensitive:reference.md:18:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "reference.md",
"line_start": 18,
"line_end": 18,
"snippet": "- Never commit real API keys to `.env`."
},
{
"id": "sensitive:reference.md:22:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "reference.md",
"line_start": 22,
"line_end": 22,
"snippet": "- In production (Vercel), variables from `.env.local` must be added to the **Project Settings > En"
},
{
"id": "sensitive:reference.md:23:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "reference.md",
"line_start": 23,
"line_end": 23,
"snippet": "- Variables in `.env` are automatically picked up if the file is committed, but usually, it's bett"
},
{
"id": "sensitive:reference.md:29:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "reference.md",
"line_start": 29,
"line_end": 29,
"snippet": "`.env`:"
},
{
"id": "sensitive:reference.md:42:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "reference.md",
"line_start": 42,
"line_end": 42,
"snippet": "`.env.local`:"
},
{
"id": "sensitive:reference.md:8:environment-variant-files",
"category": "sensitive",
"severity": "high",
"pattern": "Environment variant files",
"file": "reference.md",
"line_start": 8,
"line_end": 8,
"snippet": "| `.env.local` | Ignored 🚫 | **Secrets & Overrides** | `KEY=\"sk-123...\"`<br>`KEY=\"override\"` |"
},
{
"id": "sensitive:reference.md:22:environment-variant-files",
"category": "sensitive",
"severity": "high",
"pattern": "Environment variant files",
"file": "reference.md",
"line_start": 22,
"line_end": 22,
"snippet": "- In production (Vercel), variables from `.env.local` must be added to the **Project Settings > En"
},
{
"id": "sensitive:reference.md:42:environment-variant-files",
"category": "sensitive",
"severity": "high",
"pattern": "Environment variant files",
"file": "reference.md",
"line_start": 42,
"line_end": 42,
"snippet": "`.env.local`:"
},
{
"id": "external_commands:SKILL.md:9:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 9,
"line_end": 9,
"snippet": "1. **NO `.env.example`**: Do not create this file. Use `.env` as the template."
},
{
"id": "external_commands:SKILL.md:10:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 10,
"line_end": 10,
"snippet": "2. **Secrets in `.env.local`**: Actual sensitive values must live in `.env.local` (git-ignored)."
},
{
"id": "external_commands:SKILL.md:11:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 11,
"line_end": 11,
"snippet": "3. **Placeholders**: Every variable in `.env.local` MUST have a corresponding entry in `.env`."
},
{
"id": "external_commands:SKILL.md:12:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 12,
"line_end": 12,
"snippet": "- If sensitive: `KEY=\"\"`"
},
{
"id": "external_commands:SKILL.md:13:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 13,
"line_end": 13,
"snippet": "- If public/common: `KEY=\"default_value\"`"
},
{
"id": "external_commands:SKILL.md:18:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 18,
"line_end": 18,
"snippet": "When you need to add a secret (e.g., `REPLICATE_API_TOKEN`):"
},
{
"id": "external_commands:SKILL.md:20:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 20,
"line_end": 20,
"snippet": "1. **Update `.env`**:"
},
{
"id": "external_commands:SKILL.md:22:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 22,
"line_end": 25,
"snippet": "```bash"
},
{
"id": "external_commands:SKILL.md:25:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 25,
"line_end": 29,
"snippet": "```"
},
{
"id": "external_commands:SKILL.md:29:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 29,
"line_end": 29,
"snippet": "> \"I have added `REPLICATE_API_TOKEN` to your `.env` file. Please open `.env.local` and add the actu"
},
{
"id": "external_commands:SKILL.md:32:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 32,
"line_end": 34,
"snippet": "When adding a public or configuration variable (e.g., `NEXT_PUBLIC_APP_URL`):"
},
{
"id": "external_commands:SKILL.md:34:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 34,
"line_end": 36,
"snippet": "1. **Update `.env`**:"
},
{
"id": "external_commands:SKILL.md:36:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 36,
"line_end": 39,
"snippet": "```bash"
},
{
"id": "external_commands:SKILL.md:39:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 39,
"line_end": 42,
"snippet": "```"
},
{
"id": "external_commands:SKILL.md:42:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 42,
"line_end": 43,
"snippet": "- Server-side: `process.env.KEY`"
},
{
"id": "external_commands:SKILL.md:43:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 43,
"line_end": 46,
"snippet": "- Client-side: `process.env.NEXT_PUBLIC_KEY`"
},
{
"id": "external_commands:SKILL.md:46:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 46,
"line_end": 47,
"snippet": "- [ ] Is the variable in `.env`?"
},
{
"id": "external_commands:SKILL.md:47:ruby-shell-backtick-execution",
"category": "external_commands",
"severity": "medium",
"pattern": "Ruby/shell backtick execution",
"file": "SKILL.md",
"line_start": 47,
"line_end": 48,
"snippet": "- [ ] If sensitive, is the value in `.env` empty?"
},
{
"id": "network:SKILL.md:38:hardcoded-url",
"category": "network",
"severity": "low",
"pattern": "Hardcoded URL",
"file": "SKILL.md",
"line_start": 38,
"line_end": 38,
"snippet": "NEXT_PUBLIC_APP_URL=\"http://localhost:3000\""
},
{
"id": "env_access:SKILL.md:42:environment-variable-access-dot-notation",
"category": "env_access",
"severity": "low",
"pattern": "Environment variable access (dot notation)",
"file": "SKILL.md",
"line_start": 42,
"line_end": 42,
"snippet": "- Server-side: `process.env.KEY`"
},
{
"id": "env_access:SKILL.md:43:environment-variable-access-dot-notation",
"category": "env_access",
"severity": "low",
"pattern": "Environment variable access (dot notation)",
"file": "SKILL.md",
"line_start": 43,
"line_end": 43,
"snippet": "- Client-side: `process.env.NEXT_PUBLIC_KEY`"
},
{
"id": "env_access:SKILL.md:42:environment-variable-object",
"category": "env_access",
"severity": "low",
"pattern": "Environment variable object",
"file": "SKILL.md",
"line_start": 42,
"line_end": 42,
"snippet": "- Server-side: `process.env.KEY`"
},
{
"id": "env_access:SKILL.md:43:environment-variable-object",
"category": "env_access",
"severity": "low",
"pattern": "Environment variable object",
"file": "SKILL.md",
"line_start": 43,
"line_end": 43,
"snippet": "- Client-side: `process.env.NEXT_PUBLIC_KEY`"
},
{
"id": "sensitive:SKILL.md:3:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 3,
"line_end": 3,
"snippet": "description: Manage environment variables securely. Handles distinction between .env (template) and "
},
{
"id": "sensitive:SKILL.md:9:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 9,
"line_end": 9,
"snippet": "1. **NO `.env.example`**: Do not create this file. Use `.env` as the template."
},
{
"id": "sensitive:SKILL.md:10:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 10,
"line_end": 10,
"snippet": "2. **Secrets in `.env.local`**: Actual sensitive values must live in `.env.local` (git-ignored)."
},
{
"id": "sensitive:SKILL.md:11:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 11,
"line_end": 11,
"snippet": "3. **Placeholders**: Every variable in `.env.local` MUST have a corresponding entry in `.env`."
},
{
"id": "sensitive:SKILL.md:20:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 20,
"line_end": 20,
"snippet": "1. **Update `.env`**:"
},
{
"id": "sensitive:SKILL.md:23:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 23,
"line_end": 23,
"snippet": "# .env"
},
{
"id": "sensitive:SKILL.md:29:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 29,
"line_end": 29,
"snippet": "> \"I have added `REPLICATE_API_TOKEN` to your `.env` file. Please open `.env.local` and add the actu"
},
{
"id": "sensitive:SKILL.md:34:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 34,
"line_end": 34,
"snippet": "1. **Update `.env`**:"
},
{
"id": "sensitive:SKILL.md:37:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 37,
"line_end": 37,
"snippet": "# .env"
},
{
"id": "sensitive:SKILL.md:42:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 42,
"line_end": 42,
"snippet": "- Server-side: `process.env.KEY`"
},
{
"id": "sensitive:SKILL.md:43:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 43,
"line_end": 43,
"snippet": "- Client-side: `process.env.NEXT_PUBLIC_KEY`"
},
{
"id": "sensitive:SKILL.md:46:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 46,
"line_end": 46,
"snippet": "- [ ] Is the variable in `.env`?"
},
{
"id": "sensitive:SKILL.md:47:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 47,
"line_end": 47,
"snippet": "- [ ] If sensitive, is the value in `.env` empty?"
},
{
"id": "sensitive:SKILL.md:48:environment-file-access",
"category": "sensitive",
"severity": "high",
"pattern": "Environment file access",
"file": "SKILL.md",
"line_start": 48,
"line_end": 48,
"snippet": "- [ ] Did I ask the user to update `.env.local`?"
},
{
"id": "sensitive:SKILL.md:3:environment-variant-files",
"category": "sensitive",
"severity": "high",
"pattern": "Environment variant files",
"file": "SKILL.md",
"line_start": 3,
"line_end": 3,
"snippet": "description: Manage environment variables securely. Handles distinction between .env (template) and "
},
{
"id": "sensitive:SKILL.md:10:environment-variant-files",
"category": "sensitive",
"severity": "high",
"pattern": "Environment variant files",
"file": "SKILL.md",
"line_start": 10,
"line_end": 10,
"snippet": "2. **Secrets in `.env.local`**: Actual sensitive values must live in `.env.local` (git-ignored)."
},
{
"id": "sensitive:SKILL.md:11:environment-variant-files",
"category": "sensitive",
"severity": "high",
"pattern": "Environment variant files",
"file": "SKILL.md",
"line_start": 11,
"line_end": 11,
"snippet": "3. **Placeholders**: Every variable in `.env.local` MUST have a corresponding entry in `.env`."
},
{
"id": "sensitive:SKILL.md:29:environment-variant-files",
"category": "sensitive",
"severity": "high",
"pattern": "Environment variant files",
"file": "SKILL.md",
"line_start": 29,
"line_end": 29,
"snippet": "> \"I have added `REPLICATE_API_TOKEN` to your `.env` file. Please open `.env.local` and add the actu"
},
{
"id": "sensitive:SKILL.md:48:environment-variant-files",
"category": "sensitive",
"severity": "high",
"pattern": "Environment variant files",
"file": "SKILL.md",
"line_start": 48,
"line_end": 48,
"snippet": "- [ ] Did I ask the user to update `.env.local`?"
},
{
"id": "blocker:SKILL.md:48:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "SKILL.md",
"line_start": 48,
"line_end": 48,
"snippet": "- [ ] Did I ask the user to update `.env.local`?"
}
],
"finding_verdicts": [
{
"id": "network:reference.md:36:hardcoded-url",
"verdict": "false_positive",
"confidence": 0.94,
"reason": "This is a localhost development URL shown as an example default. It does not make a network request or send data externally."
},
{
"id": "env_access:reference.md:32:database-connection-strings",
"verdict": "false_positive",
"confidence": 0.93,
"reason": "The database variable is an empty template placeholder in the committed .env example. No actual credential value is present."
},
{
"id": "env_access:reference.md:45:database-connection-strings",
"verdict": "false_positive",
"confidence": 0.78,
"reason": "The PostgreSQL URL is a dummy localhost example with placeholder user and password text. It is credential-shaped, but there is no evidence of a live secret."
},
{
"id": "env_access:reference.md:14:generic-api-secret-keys",
"verdict": "false_positive",
"confidence": 0.9,
"reason": "This line documents naming conventions for server secrets. It does not expose or read an API key."
},
{
"id": "sensitive:reference.md:7:environment-file-access",
"verdict": "confirmed",
"confidence": 0.82,
"severity": "high",
"reason": "The reference defines .env as a committed template for secret placeholders. This is legitimate, but it still directs agents toward sensitive configuration files that need strict handling."
},
{
"id": "sensitive:reference.md:8:environment-file-access",
"verdict": "confirmed",
"confidence": 0.86,
"severity": "high",
"reason": "The reference identifies .env.local as the location for real secrets and overrides. Skills that operate near this file can expose credentials if they read or print values."
},
{
"id": "sensitive:reference.md:9:environment-file-access",
"verdict": "false_positive",
"confidence": 0.92,
"reason": "This line forbids .env.example and does not access secrets. It is a project convention rather than sensitive file handling."
},
{
"id": "sensitive:reference.md:18:environment-file-access",
"verdict": "false_positive",
"confidence": 0.96,
"reason": "The line warns users not to commit real API keys. It is protective guidance, not secret access."
},
{
"id": "sensitive:reference.md:22:environment-file-access",
"verdict": "confirmed",
"confidence": 0.78,
"severity": "high",
"reason": "The line discusses copying .env.local values into Vercel settings. That workflow handles production secrets and requires user-controlled entry to avoid disclosure."
},
{
"id": "sensitive:reference.md:23:environment-file-access",
"verdict": "confirmed",
"confidence": 0.72,
"severity": "high",
"reason": "The line discusses committed .env variables and deployment behavior. It is legitimate guidance, but mistakes could publish sensitive defaults."
},
{
"id": "sensitive:reference.md:29:environment-file-access",
"verdict": "confirmed",
"confidence": 0.76,
"severity": "high",
"reason": "The example begins a .env block that includes secret placeholders. It is a safe pattern only if real values remain absent."
},
{
"id": "sensitive:reference.md:42:environment-file-access",
"verdict": "confirmed",
"confidence": 0.88,
"severity": "high",
"reason": "The example begins a .env.local block, which is explicitly the local secrets file. Handling this file is sensitive even when the shown values are examples."
},
{
"id": "sensitive:reference.md:8:environment-variant-files",
"verdict": "confirmed",
"confidence": 0.86,
"severity": "high",
"reason": "This line names .env.local as the secrets and overrides file. That is a real sensitive-file scope even though the examples are placeholders."
},
{
"id": "sensitive:reference.md:22:environment-variant-files",
"verdict": "confirmed",
"confidence": 0.78,
"severity": "high",
"reason": "The deployment note involves moving .env.local values into hosted environment settings. The workflow touches production secrets and needs explicit safeguards."
},
{
"id": "sensitive:reference.md:42:environment-variant-files",
"verdict": "confirmed",
"confidence": 0.88,
"severity": "high",
"reason": "The referenced .env.local example is the secret-bearing environment variant. This is sensitive context, not ordinary documentation only."
},
{
"id": "external_commands:SKILL.md:9:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The backticks are markdown formatting around .env.example and .env. There is no Ruby or shell execution."
},
{
"id": "external_commands:SKILL.md:10:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The backticks are markdown formatting around .env.local. No command is executed or suggested."
},
{
"id": "external_commands:SKILL.md:11:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The line uses markdown backticks for file names. It is not shell syntax or dynamic execution."
},
{
"id": "external_commands:SKILL.md:12:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.96,
"reason": "The backticked text is an environment variable placeholder. It is not a command and has no execution path."
},
{
"id": "external_commands:SKILL.md:13:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.96,
"reason": "The backticked text is a sample key-value placeholder. It is documentation, not executable shell content."
},
{
"id": "external_commands:SKILL.md:18:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The backticks mark an example environment variable name. There is no shell command or interpreter invocation."
},
{
"id": "external_commands:SKILL.md:20:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The backticks mark the .env filename in prose. This is not Ruby backtick execution."
},
{
"id": "external_commands:SKILL.md:22:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.95,
"reason": "This is a fenced markdown block tagged bash to show .env contents. It contains an assignment example, not an instruction to run a command."
},
{
"id": "external_commands:SKILL.md:25:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.95,
"reason": "This closes a markdown code fence near an environment variable example. No executable command appears on the cited lines."
},
{
"id": "external_commands:SKILL.md:29:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.96,
"reason": "The backticks format variable and file names inside a user-facing message. They do not perform shell execution."
},
{
"id": "external_commands:SKILL.md:32:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The backticks mark an example public variable name. There is no command execution behavior."
},
{
"id": "external_commands:SKILL.md:34:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The line formats the .env filename with markdown backticks. It is not executable syntax."
},
{
"id": "external_commands:SKILL.md:36:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.95,
"reason": "This is a markdown code fence for an environment file example. It does not instruct running a shell command."
},
{
"id": "external_commands:SKILL.md:39:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.95,
"reason": "This closes the fenced example block. The cited context is documentation, not code execution."
},
{
"id": "external_commands:SKILL.md:42:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.96,
"reason": "The backticked process.env.KEY text is accessor syntax documentation. It is not a shell command or Ruby execution."
},
{
"id": "external_commands:SKILL.md:43:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.96,
"reason": "The backticked client-side process.env example is documentation. No external command is executed."
},
{
"id": "external_commands:SKILL.md:46:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The backticks format the .env filename inside a checklist item. This is not command execution."
},
{
"id": "external_commands:SKILL.md:47:ruby-shell-backtick-execution",
"verdict": "false_positive",
"confidence": 0.97,
"reason": "The backticks format .env in a checklist question. There is no command or interpreter use."
},
{
"id": "network:SKILL.md:38:hardcoded-url",
"verdict": "false_positive",
"confidence": 0.94,
"reason": "The URL is a localhost default for a public app URL example. It does not create an outbound network operation."
},
{
"id": "env_access:SKILL.md:42:environment-variable-access-dot-notation",
"verdict": "false_positive",
"confidence": 0.9,
"reason": "The line documents server-side access syntax. It does not read a real environment variable or expose a value."
},
{
"id": "env_access:SKILL.md:43:environment-variable-access-dot-notation",
"verdict": "false_positive",
"confidence": 0.9,
"reason": "The line documents client-side public variable syntax. It does not access or disclose any actual secret."
},
{
"id": "env_access:SKILL.md:42:environment-variable-object",
"verdict": "false_positive",
"confidence": 0.9,
"reason": "The process.env text is documentation for server-side code. There is no executing code path in the skill file."
},
{
"id": "env_access:SKILL.md:43:environment-variable-object",
"verdict": "false_positive",
"confidence": 0.9,
"reason": "The process.env text is a public client-side naming example. It is not live environment access."
},
{
"id": "sensitive:SKILL.md:3:environment-file-access",
"verdict": "confirmed",
"confidence": 0.83,
"severity": "high",
"reason": "The skill description states it manages .env and .env.local distinctions. This is legitimate but confirms sensitive environment-file scope."
},
{
"id": "sensitive:SKILL.md:9:environment-file-access",
"verdict": "confirmed",
"confidence": 0.76,
"severity": "high",
"reason": "The instruction directs use of .env as the template file. Editing committed environment templates can leak secrets if safeguards are not followed."
},
{
"id": "sensitive:SKILL.md:10:environment-file-access",
"verdict": "confirmed",
"confidence": 0.88,
"severity": "high",
"reason": "The instruction explicitly identifies .env.local as the file holding actual sensitive values. Any agent workflow around that file requires caution."
},
{
"id": "sensitive:SKILL.md:11:environment-file-access",
"verdict": "confirmed",
"confidence": 0.84,
"severity": "high",
"reason": "The rule maps .env.local entries to .env placeholders. That requires reasoning about secret-bearing variables and can expose names or values if mishandled."
},
{
"id": "sensitive:SKILL.md:20:environment-file-access",
"verdict": "confirmed",
"confidence": 0.8,
"severity": "high",
"reason": "The workflow tells the agent to update .env when adding a secret. This is sensitive configuration editing even when the intended value is empty."
},
{
"id": "sensitive:SKILL.md:23:environment-file-access",
"verdict": "confirmed",
"confidence": 0.76,
"severity": "high",
"reason": "The cited .env example is part of the secret-variable workflow. It is safe only when the placeholder remains empty and no secret is committed."
},
{
"id": "sensitive:SKILL.md:29:environment-file-access",
"verdict": "confirmed",
"confidence": 0.86,
"severity": "high",
"reason": "The instruction asks the user to add an actual token to .env.local. That is appropriate user-controlled handling, but it still concerns a secret-bearing file."
},
{
"id": "sensitive:SKILL.md:34:environment-file-access",
"verdict": "confirmed",
"confidence": 0.74,
"severity": "high",
"reason": "The workflow directs edits to .env for configuration variables. It is lower concern than secrets, but still environment file modification."
},
{
"id": "sensitive:SKILL.md:37:environment-file-access",
"verdict": "confirmed",
"confidence": 0.74,
"severity": "high",
"reason": "The cited .env example is an environment file block. It is a template example, but edits to this file can affect committed configuration."
},
{
"id": "sensitive:SKILL.md:42:environment-file-access",
"verdict": "false_positive",
"confidence": 0.88,
"reason": "The line documents process.env.KEY syntax and does not refer to opening or modifying an environment file. It is not sensitive file access."
},
{
"id": "sensitive:SKILL.md:43:environment-file-access",
"verdict": "false_positive",
"confidence": 0.88,
"reason": "The line documents NEXT_PUBLIC client-side syntax. It does not access an environment file or expose an actual value."
},
{
"id": "sensitive:SKILL.md:46:environment-file-access",
"verdict": "confirmed",
"confidence": 0.74,
"severity": "high",
"reason": "The checklist requires checking whether a variable is in .env. This confirms the skill operates on environment files."
},
{
"id": "sensitive:SKILL.md:47:environment-file-access",
"verdict": "confirmed",
"confidence": 0.8,
"severity": "high",
"reason": "The checklist verifies that sensitive .env values are empty. That is good practice, but it still requires sensitive placeholder review."
},
{
"id": "sensitive:SKILL.md:48:environment-file-access",
"verdict": "confirmed",
"confidence": 0.86,
"severity": "high",
"reason": "The checklist asks whether the user updated .env.local. This confirms the workflow touches the secret-file process."
},
{
"id": "sensitive:SKILL.md:3:environment-variant-files",
"verdict": "confirmed",
"confidence": 0.83,
"severity": "high",
"reason": "The skill description distinguishes .env from .env.local. This confirms environment variant file handling within the skill scope."
},
{
"id": "sensitive:SKILL.md:10:environment-variant-files",
"verdict": "confirmed",
"confidence": 0.88,
"severity": "high",
"reason": "The rule states actual sensitive values must live in .env.local. This is a real secret-file workflow, not an unrelated mention."
},
{
"id": "sensitive:SKILL.md:11:environment-variant-files",
"verdict": "confirmed",
"confidence": 0.84,
"severity": "high",
"reason": "The rule links .env.local entries to .env placeholders. That variant-file relationship is sensitive because it tracks secret-bearing variables."
},
{
"id": "sensitive:SKILL.md:29:environment-variant-files",
"verdict": "confirmed",
"confidence": 0.86,
"severity": "high",
"reason": "The user-facing message directs secret entry into .env.local. The skill avoids asking for the value in chat, but the file remains sensitive."
},
{
"id": "sensitive:SKILL.md:48:environment-variant-files",
"verdict": "confirmed",
"confidence": 0.86,
"severity": "high",
"reason": "The checklist explicitly includes .env.local update confirmation. This is sensitive environment variant handling."
},
{
"id": "blocker:SKILL.md:48:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.98,
"reason": "The phrase asks whether the user was prompted to update .env.local. It is not host reconnaissance or system information gathering."
}
],
"semantic_findings": [],
"critical_findings": [],
"high_findings": [
{
"title": "Environment file access",
"description": "| `.env` | Committed ✅ | **Template & Defaults** | `KEY=\"\"` (Secrets)<br>`KEY=\"val\"` (Defaults) |",
"locations": [
{
"file": "reference.md",
"line_start": 7,
"line_end": 7
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.82,
"confidence_reasoning": "The reference defines .env as a committed template for secret placeholders. This is legitimate, but it still directs agents toward sensitive configuration files that need strict handling."
},
{
"title": "Environment file access",
"description": "| `.env.local` | Ignored 🚫 | **Secrets & Overrides** | `KEY=\"sk-123...\"`<br>`KEY=\"override\"` |",
"locations": [
{
"file": "reference.md",
"line_start": 8,
"line_end": 8
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.86,
"confidence_reasoning": "The reference identifies .env.local as the location for real secrets and overrides. Skills that operate near this file can expose credentials if they read or print values."
},
{
"title": "Environment file access",
"description": "- In production (Vercel), variables from `.env.local` must be added to the **Project Settings > En",
"locations": [
{
"file": "reference.md",
"line_start": 22,
"line_end": 22
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.78,
"confidence_reasoning": "The line discusses copying .env.local values into Vercel settings. That workflow handles production secrets and requires user-controlled entry to avoid disclosure."
},
{
"title": "Environment file access",
"description": "- Variables in `.env` are automatically picked up if the file is committed, but usually, it's bett",
"locations": [
{
"file": "reference.md",
"line_start": 23,
"line_end": 23
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.72,
"confidence_reasoning": "The line discusses committed .env variables and deployment behavior. It is legitimate guidance, but mistakes could publish sensitive defaults."
},
{
"title": "Environment file access",
"description": "`.env`:",
"locations": [
{
"file": "reference.md",
"line_start": 29,
"line_end": 29
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.76,
"confidence_reasoning": "The example begins a .env block that includes secret placeholders. It is a safe pattern only if real values remain absent."
},
{
"title": "Environment file access",
"description": "`.env.local`:",
"locations": [
{
"file": "reference.md",
"line_start": 42,
"line_end": 42
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.88,
"confidence_reasoning": "The example begins a .env.local block, which is explicitly the local secrets file. Handling this file is sensitive even when the shown values are examples."
},
{
"title": "Environment variant files",
"description": "| `.env.local` | Ignored 🚫 | **Secrets & Overrides** | `KEY=\"sk-123...\"`<br>`KEY=\"override\"` |",
"locations": [
{
"file": "reference.md",
"line_start": 8,
"line_end": 8
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.86,
"confidence_reasoning": "This line names .env.local as the secrets and overrides file. That is a real sensitive-file scope even though the examples are placeholders."
},
{
"title": "Environment variant files",
"description": "- In production (Vercel), variables from `.env.local` must be added to the **Project Settings > En",
"locations": [
{
"file": "reference.md",
"line_start": 22,
"line_end": 22
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.78,
"confidence_reasoning": "The deployment note involves moving .env.local values into hosted environment settings. The workflow touches production secrets and needs explicit safeguards."
},
{
"title": "Environment variant files",
"description": "`.env.local`:",
"locations": [
{
"file": "reference.md",
"line_start": 42,
"line_end": 42
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.88,
"confidence_reasoning": "The referenced .env.local example is the secret-bearing environment variant. This is sensitive context, not ordinary documentation only."
},
{
"title": "Environment file access",
"description": "description: Manage environment variables securely. Handles distinction between .env (template) and ",
"locations": [
{
"file": "SKILL.md",
"line_start": 3,
"line_end": 3
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.83,
"confidence_reasoning": "The skill description states it manages .env and .env.local distinctions. This is legitimate but confirms sensitive environment-file scope."
},
{
"title": "Environment file access",
"description": "1. **NO `.env.example`**: Do not create this file. Use `.env` as the template.",
"locations": [
{
"file": "SKILL.md",
"line_start": 9,
"line_end": 9
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.76,
"confidence_reasoning": "The instruction directs use of .env as the template file. Editing committed environment templates can leak secrets if safeguards are not followed."
},
{
"title": "Environment file access",
"description": "2. **Secrets in `.env.local`**: Actual sensitive values must live in `.env.local` (git-ignored).",
"locations": [
{
"file": "SKILL.md",
"line_start": 10,
"line_end": 10
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.88,
"confidence_reasoning": "The instruction explicitly identifies .env.local as the file holding actual sensitive values. Any agent workflow around that file requires caution."
},
{
"title": "Environment file access",
"description": "3. **Placeholders**: Every variable in `.env.local` MUST have a corresponding entry in `.env`.",
"locations": [
{
"file": "SKILL.md",
"line_start": 11,
"line_end": 11
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.84,
"confidence_reasoning": "The rule maps .env.local entries to .env placeholders. That requires reasoning about secret-bearing variables and can expose names or values if mishandled."
},
{
"title": "Environment file access",
"description": "1. **Update `.env`**:",
"locations": [
{
"file": "SKILL.md",
"line_start": 20,
"line_end": 20
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.8,
"confidence_reasoning": "The workflow tells the agent to update .env when adding a secret. This is sensitive configuration editing even when the intended value is empty."
},
{
"title": "Environment file access",
"description": "# .env",
"locations": [
{
"file": "SKILL.md",
"line_start": 23,
"line_end": 23
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.76,
"confidence_reasoning": "The cited .env example is part of the secret-variable workflow. It is safe only when the placeholder remains empty and no secret is committed."
},
{
"title": "Environment file access",
"description": "> \"I have added `REPLICATE_API_TOKEN` to your `.env` file. Please open `.env.local` and add the actu",
"locations": [
{
"file": "SKILL.md",
"line_start": 29,
"line_end": 29
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.86,
"confidence_reasoning": "The instruction asks the user to add an actual token to .env.local. That is appropriate user-controlled handling, but it still concerns a secret-bearing file."
},
{
"title": "Environment file access",
"description": "1. **Update `.env`**:",
"locations": [
{
"file": "SKILL.md",
"line_start": 34,
"line_end": 34
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.74,
"confidence_reasoning": "The workflow directs edits to .env for configuration variables. It is lower concern than secrets, but still environment file modification."
},
{
"title": "Environment file access",
"description": "# .env",
"locations": [
{
"file": "SKILL.md",
"line_start": 37,
"line_end": 37
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.74,
"confidence_reasoning": "The cited .env example is an environment file block. It is a template example, but edits to this file can affect committed configuration."
},
{
"title": "Environment file access",
"description": "- [ ] Is the variable in `.env`?",
"locations": [
{
"file": "SKILL.md",
"line_start": 46,
"line_end": 46
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.74,
"confidence_reasoning": "The checklist requires checking whether a variable is in .env. This confirms the skill operates on environment files."
},
{
"title": "Environment file access",
"description": "- [ ] If sensitive, is the value in `.env` empty?",
"locations": [
{
"file": "SKILL.md",
"line_start": 47,
"line_end": 47
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.8,
"confidence_reasoning": "The checklist verifies that sensitive .env values are empty. That is good practice, but it still requires sensitive placeholder review."
},
{
"title": "Environment file access",
"description": "- [ ] Did I ask the user to update `.env.local`?",
"locations": [
{
"file": "SKILL.md",
"line_start": 48,
"line_end": 48
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.86,
"confidence_reasoning": "The checklist asks whether the user updated .env.local. This confirms the workflow touches the secret-file process."
},
{
"title": "Environment variant files",
"description": "description: Manage environment variables securely. Handles distinction between .env (template) and ",
"locations": [
{
"file": "SKILL.md",
"line_start": 3,
"line_end": 3
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.83,
"confidence_reasoning": "The skill description distinguishes .env from .env.local. This confirms environment variant file handling within the skill scope."
},
{
"title": "Environment variant files",
"description": "2. **Secrets in `.env.local`**: Actual sensitive values must live in `.env.local` (git-ignored).",
"locations": [
{
"file": "SKILL.md",
"line_start": 10,
"line_end": 10
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.88,
"confidence_reasoning": "The rule states actual sensitive values must live in .env.local. This is a real secret-file workflow, not an unrelated mention."
},
{
"title": "Environment variant files",
"description": "3. **Placeholders**: Every variable in `.env.local` MUST have a corresponding entry in `.env`.",
"locations": [
{
"file": "SKILL.md",
"line_start": 11,
"line_end": 11
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.84,
"confidence_reasoning": "The rule links .env.local entries to .env placeholders. That variant-file relationship is sensitive because it tracks secret-bearing variables."
},
{
"title": "Environment variant files",
"description": "> \"I have added `REPLICATE_API_TOKEN` to your `.env` file. Please open `.env.local` and add the actu",
"locations": [
{
"file": "SKILL.md",
"line_start": 29,
"line_end": 29
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.86,
"confidence_reasoning": "The user-facing message directs secret entry into .env.local. The skill avoids asking for the value in chat, but the file remains sensitive."
},
{
"title": "Environment variant files",
"description": "- [ ] Did I ask the user to update `.env.local`?",
"locations": [
{
"file": "SKILL.md",
"line_start": 48,
"line_end": 48
}
],
"review_kind": "security",
"source_category": "sensitive",
"source_severity": "high",
"confidence": 0.86,
"confidence_reasoning": "The checklist explicitly includes .env.local update confirmation. This is sensitive environment variant handling."
}
],
"medium_findings": [],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 2,
"total_lines": 99,
"audit_model": "codex",
"audited_at": "2026-07-04T23:49:47.349Z",
"agent_auto_install_policy": "confirmation_required",
"manual_install_policy": "allowed"
},
"content": {
"user_title": "Manage Environment Variables Securely",
"value_statement": "Environment variables often mix public defaults with private secrets. This skill guides Claude, Codex, and Claude Code to keep templates separate from local secrets.",
"seo_keywords": [
"Claude",
"Codex",
"Claude Code",
"environment variables",
".env",
".env.local",
"secret management",
"Next.js env",
"Vercel environment variables",
"developer workflow"
],
"actual_capabilities": [
"Defines .env as the committed template for defaults and empty secret placeholders.",
"Defines .env.local as the ignored file for real local secrets and overrides.",
"Provides steps for adding a new sensitive variable without placing the value in .env.",
"Provides steps for adding public or non-sensitive configuration values.",
"Documents server-side and client-side environment variable naming conventions.",
"Includes a checklist for reviewing environment variable changes."
],
"limitations": [
"Does not rotate leaked secrets or manage cloud provider accounts.",
"Does not validate whether environment values are correct at runtime.",
"Requires user review before editing real project environment files.",
"Focuses on Next.js and Vercel-style environment conventions."
],
"use_cases": [
{
"title": "Add a Secret Safely",
"description": "Add a new API token placeholder to the project template while keeping the actual value in a local ignored file.",
"target_user": "Application developer"
},
{
"title": "Standardize Deployment Variables",
"description": "Review which variables belong in committed templates, local overrides, and hosted deployment settings.",
"target_user": "DevOps engineer"
},
{
"title": "Review Configuration Changes",
"description": "Check an environment variable change for secret exposure before code review or release.",
"target_user": "Code reviewer"
}
],
"prompt_templates": [
{
"title": "Add a New Secret",
"scenario": "Beginner task for one sensitive variable.",
"prompt": "Add a placeholder for a new sensitive variable named PAYMENT_API_KEY. Keep the real value out of committed files and tell me where to enter it locally."
},
{
"title": "Add a Public Setting",
"scenario": "Basic task for a non-sensitive client setting.",
"prompt": "Add a public application URL setting for local development. Use the project environment conventions from this skill."
},
{
"title": "Audit Existing Variables",
"scenario": "Intermediate review of environment file structure.",
"prompt": "Review the current environment variable setup. Identify which entries should be templates, local secrets, public values, or deployment settings."
},
{
"title": "Prepare Deployment Checklist",
"scenario": "Advanced release preparation across local and hosted environments.",
"prompt": "Prepare a release checklist for environment variables before deployment. Include template placeholders, local secrets, hosted variables, and final safety checks."
}
],
"output_examples": [
{
"input": "Add a sensitive token for a new image generation provider.",
"output": "The assistant adds an empty template entry, then asks the user to place the real token in the local ignored secrets file."
},
{
"input": "Review environment variables before deploying to Vercel.",
"output": "The assistant separates public defaults, empty secret placeholders, and hosted production variables, then lists any missing setup steps."
},
{
"input": "Check whether a new variable is safe to commit.",
"output": "The assistant explains whether the value is public or sensitive and recommends an empty placeholder when the value must remain private."
}
],
"best_practices": [
"Keep committed template files free of real secret values.",
"Ask users to enter secrets locally instead of sending them through chat.",
"Review environment file changes before committing or deploying."
],
"anti_patterns": [
"Do not place live API keys, tokens, or passwords in committed environment files.",
"Do not ask users to paste secret values into the conversation.",
"Do not create duplicate environment templates when the project standard uses .env."
],
"faq": [
{
"question": "Does this skill manage real secret values?",
"answer": "No. It guides where secrets should live, but users should enter real values locally."
},
{
"question": "Can it create a .env.example file?",
"answer": "No. The documented convention forbids .env.example and uses .env as the template."
},
{
"question": "Is it suitable for public client variables?",
"answer": "Yes. It includes guidance for public variables that use the NEXT_PUBLIC prefix."
},
{
"question": "Does it support Vercel deployment settings?",
"answer": "Yes. It reminds users to configure production variables in Vercel project settings."
},
{
"question": "Will it detect leaked credentials automatically?",
"answer": "No. It provides process guidance, but separate secret scanning is still needed."
},
{
"question": "Which assistants can use this skill?",
"answer": "The report lists support for Claude, Codex, and Claude Code."
}
]
},
"file_structure": [
{
"name": "reference.md",
"type": "file",
"path": "reference.md",
"lines": 49
},
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 50
}
]
}
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: 472k | 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: 472k | 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: 472k | 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 |