check-env-keys

Compare environment variable keys across .env files and shell against templates.

1|Updated Oct 30, 2025
One-click install
npx skills add https://github.com/iamladi/cautious-computing-machine--primitives-plugin --skill check-env-keys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-env-keys
Source: https://github.com/iamladi/cautious-computing-machine--primitives-plugin/tree/main/skills/check-env-keys
Command: npx skills add https://github.com/iamladi/cautious-computing-machine--primitives-plugin --skill check-env-keys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill lets you verify which environment variable keys exist in .env files or shell environment without exposing their values.

Core Features & Use Cases

  • Safe key presence checks across multiple sources (.env.local, .env, and shell environment) to ensure configurations are complete.
  • Compare against template files (.env.sample, .env.example) to identify missing keys.
  • Non-verbose reporting that indicates missing keys without revealing sensitive values across environments.

Quick Start

Run the check-env-keys skill to identify which environment variable keys are present across .env.local, .env, and the shell environment.

Frequently Asked Questions about check-env-keys

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

FAQPage Schema
How do I check if environment variables exist in .env files without exposing their values?

Check environment variable keys by parsing .env.local, .env, and shell exports to confirm key presence without exposing values. The process compares configurations against template files and outputs a safe, non-verbose report of missing keys.

What is the best way to find missing keys in a .env file compared to a template?

Finding missing keys involves comparing your .env files and shell environment against a template like .env.sample or .env.example. This identifies which required environment variable keys are absent and generates a safe report indicating missing keys.

Can I verify environment variable consistency across shell profiles and multiple .env files?

Yes, you can verify environment variable consistency across shell profiles and multiple .env files. The process parses .env.local, .env, and shell exports, comparing them against templates to ensure configurations are complete and consistent without revealing values.

How do I safely validate dotenv keys for a project without printing secrets?

Safely validate dotenv keys by parsing env files and shell exports to check for key existence against template files. This enforces key presence and produces a non-verbose report of missing keys, ensuring sensitive values are never exposed during validation.

Does this environment variable validation work with both shell exports and dotenv files?

Yes, environment variable validation works with both shell exports and dotenv files. It parses .env.local, .env, and shell profiles to verify key presence against template files, ensuring complete configurations across all defined sources without exposing values.

What are the limitations of checking environment variable keys without exposing values?

A limitation of checking environment variable keys without exposing values is that the non-verbose report only indicates missing keys. It does not reveal sensitive values or provide detailed debugging information about incorrect values within your .env files or shell environment.