cc-skill:env-var-management

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

This skill helps you organize environment variables and secrets correctly so they don't leak, get lost, or cause production failures. It shows you where each type of variable should live (local files vs. Vercel), how to name them clearly, and which ones are safe to expose in your browser code.

who it is for

Anyone deploying a web app who needs to manage API keys, database passwords, and configuration settings across development and production.

when it fires

When you mention environment variables, secrets, API keys, .env files, NEXT_PUBLIC, secret rotation, or configuration management for your project.

say something like

"How do I set up my .env file for this Next.js project?"
"I accidentally put my Stripe secret key in NEXT_PUBLIC. What do I do?"
"Where should I store my Anthropic API key so it doesn't leak?"

what you might get back

Your .env.example file should list every variable your app needs. Public ones like NEXT_PUBLIC_SUPABASE_URL go in .env with placeholder values. Secret ones like SUPABASE_SERVICE_ROLE_KEY stay in .env.local on your computer, never checked in. In Vercel, you set production secrets via the dashboard under Project Settings. If you ever prefix a secret with NEXT_PUBLIC_, rotate that key immediately because it's now permanently exposed.

how to know it worked

You know it worked because you have a clear .env.example file documenting all variables, your .env.local is gitignored, and you can explain which secrets go where without confusion.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

from drafts

attributed

$0.00

signups + revenue

Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/env-var-management/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when working with environment variables, secrets, API keys, .env files, or Vercel/Supabase environment configuration in Jay's projects. Triggers on "env vars", "environment variables", "secrets", "API keys", ".env", "NEXT_PUBLIC", "sec

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/env-var-management/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity

never used

2026-04-03today

cost model

unitincluded

capabilities

{
  "source": "global",
  "description": "Use this skill when working with environment variables, secrets, API keys, .env files, or Vercel/Supabase environment configuration in Jay's projects. Triggers on \"env vars\", \"environment variables\", \"secrets\", \"API keys\", \".env\", \"NEXT_PUBLIC\", \"secret rotation\", or any configuration management work. Applies Jay's conventions for naming, scoping, and where each var lives."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/env-var-management/SKILL.md"
}

This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.