Skill Detail

Lint .env files for duplicated keys and unsafe formatting with dotenv-linter

<p>Check dotenv files for duplicated keys, malformed values, and formatting mistakes before they break local runs or secret handoffs.</p>

Security & VerificationMulti-Framework
Security & Verification Multi-Framework Security Reviewed
⭐ 2.1k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill lint-dotenv-files-for-duplicated-keys-and-unsafe-formatting-with-dotenv-linter Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
The dotenv-linter CLI or binary and a repository containing dotenv files to check.
Install & setup
<p>Install a release binary or build with <code>cargo install dotenv-linter</code>, then run <code>dotenv-linter</code> against the repository root or specific <code>.env</code> files. Use the documented check, fix, and diff flows to review problems before committing changes.</p>
Author
dotenv-linter
Publisher
Organization
Last updated
Apr 17, 2026
Quick brief

Use dotenv-linter when an agent needs to inspect .env files for duplicated keys, malformed delimiters, missing values, quote problems, ordering issues, and other dotenv-specific defects that cause configuration drift. It fits repo hygiene, onboarding cleanup, and pre-merge checks where environment files need to stay predictable.

How it works

What this skill actually does

A user should invoke this instead of using a secret manager or editing environment files by hand when the task is validating and normalizing dotenv syntax. The scope boundary keeps it skill-shaped: dotenv-linter audits and fixes dotenv file structure only, not secret storage, rotation, vault administration, or broader configuration management.