Manage environment variables and credentials across Node.js/Next.js projects.
npx skills add https://github.com/djnsty23/claude-auto-dev --skill env-vars
Please help me install this Agent Skill. Skill: env-vars Source: https://github.com/djnsty23/claude-auto-dev/tree/main/skills/env-vars Command: npx skills add https://github.com/djnsty23/claude-auto-dev --skill env-vars
Managing environment variables and credentials across projects is error-prone and insecure; this skill provides a structured workflow to configure, store, and reference env vars without leaking keys.
Configure and manage your project's environment variables securely.
High-intent search queries and answers about installing and using this skill.
You can securely manage environment variables by reading from process.env, avoiding hardcoded values, and generating a project-local .env.local template to structure secrets safely across development, staging, and production environments.
The best way to set up a .env.local template is to use a structured workflow that maps variables to project scope, prevents hardcoded keys, and generates guidance for referencing them in Node.js and Next.js workflows.
Check current environment variables and their sources by using a workflow that reads from process.env, identifies whether variables are system-wide or project-scoped, and maps them to prevent misconfigurations and leaks.
Yes, you can add new environment variables securely and map them to either system-wide or project scope, applying per-project overrides to prevent credential leaks and configuration conflicts across development and production stages.
Avoid hardcoding credentials because managing environment variables securely through process.env and structured .env templates prevents accidental key leaks, reduces misconfigurations, and enforces best practices across staging and production environments.
tikazyqIdentify project technology stack, testing frameworks, and environment dependencies.
matthew-johnsonRead and inject 1Password CLI secrets into applications and automation workflows.
mattbobambroseDetect committed secrets and sensitive files in git history and working tree.
wesleyegbertoManage and rotate credentials in CI/CD pipelines with HashiCorp Vault and cloud secret managers.
