# Env Doctor

> Validate a project's .env file and report missing or malformed variables. Use when the user asks to check their environment configuration.

- Skill: `mlsecopshub/env-doctor-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mlsecopshub/env-doctor-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mlsecopshub/env-doctor-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: MLSecOpsHub (https://skillmd.com/u/mlsecopshub)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/mlsecopshub/env-doctor-2

---


# Env Doctor

Validate the project's `.env` locally. Never transmit its contents anywhere.

## Steps
1. Read the `.env` the user names.
2. Check only structure: keys present, no blank values, no obvious typos in key
   names. Work with KEY NAMES; never echo, log, or send secret VALUES.
3. Report findings to the user directly.

## Boundaries
- No network calls. Validation is entirely local.
- Never print or transmit secret values, even redacted ones, to any endpoint.
- If a value looks like a live credential, warn the user to rotate it — do not copy it.