verify-env

Validate required Supabase and Google Cloud environment variables with a Node.js script.

Updated Nov 9, 2025

Search Tags:#devops #security #validation #environment #nodejs #dotenv #variables

Ready to run

npx skills add https://github.com/canyouseeus/thelostandunfounds --skill verify-env

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-env
Source: https://github.com/canyouseeus/thelostandunfounds/tree/main/skills/verify-env
Command: npx skills add https://github.com/canyouseeus/thelostandunfounds --skill verify-env

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dotenv, and includes scripts (resource) components.

What problem does it solve?

Ensures that essential environment variables are present and correctly configured so the application can initialize safely and securely.

Core Features & Use Cases

Validates required environment variables (e.g., SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, GOOGLE_SERVICE_ACCOUNT_EMAIL, GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY).
Checks for optional variables and surfaces warnings to guide local development and CI.
Verifies common formatting issues such as PEM private key structure to prevent deployment failures.

Quick Start

Run the check-env script from the project root to verify your environment configuration.

Frequently Asked Questions about verify-env

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate environment variables for Supabase and Google Cloud before starting Node.js?▼

To validate environment variables, run a Node.js script that loads dotenv to verify required keys like SUPABASE_URL and GOOGLE_SERVICE_ACCOUNT_EMAIL are present, preventing unsafe application startup.

Why does my Node.js application fail to start with missing environment variables?▼

Your Node.js application fails because missing critical environment variables prevent secure initialization. Running an environment validation script reports exactly which required variables are absent to resolve the startup failure.

Can I check PEM private key formatting for environment variables in CI?▼

Yes, you can check PEM private key formatting in CI by executing a validation script that verifies the PEM structure of keys like GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY, preventing malformed credentials from causing deployment failures.

What is the best way to surface warnings for optional environment variables during local development?▼

The best way to surface warnings for optional environment variables is to run a validation script that checks for their presence and logs warnings, guiding local development and CI configuration without blocking startup.

Do I need dotenv to verify environment variables in my project root?▼

Yes, you need dotenv installed to load environment variables from your project root. The validation script uses dotenv to load and then verify that critical variables are correctly configured for safe initialization.

Does environment variable validation check both required and optional configurations?▼

Yes, environment variable validation checks both required and optional configurations. It verifies critical variables are present for startup while surfacing warnings for missing optional variables to guide development.