Check dotenv files for duplicated keys, malformed values, and formatting mistakes before they break local runs or secret handoffs.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add aibot88/sec_skill_store --skill lint-dotenv-files-for-duplicated-keys-and-unsafe-formatting-with --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Lint Dotenv Files For Duplicated Keys And Unsafe Formatting With?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/aibot88-lint-dotenv-files-for-duplicated-keys-and-unsafe-f)More formats (shields.io, HTML) on the badges page.
---
title: "Lint .env files for duplicated keys and unsafe formatting with dotenv-linter"
description: "Check dotenv files for duplicated keys, malformed values, and formatting mistakes before they break local runs or secret handoffs."
verification: "listed"
source: "https://github.com/dotenv-linter/dotenv-linter"
author: "dotenv-linter"
publisher_type: "organization"
category:
- "Security & Verification"
framework:
- "Multi-Framework"
tool_ecosystem:
github_repo: "dotenv-linter/dotenv-linter"
github_stars: 2068
---
# Lint .env files for duplicated keys and unsafe formatting with dotenv-linter
Check dotenv files for duplicated keys, malformed values, and formatting mistakes before they break local runs or secret handoffs.
## Prerequisites
The dotenv-linter CLI or binary and a repository containing dotenv files to check.
## Installation
Choose whichever fits your setup:
1. Copy this skill folder into your local skills directory.
2. Clone the repo and symlink or copy the skill into your agent workspace.
3. Add the repo as a git submodule if you manage shared skills centrally.
4. Install it through your internal provisioning or packaging workflow.
5. Download the folder directly from GitHub and place it in your skills collection.
Install command or upstream instructions:
```
<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>
```
## Documentation
- https://dotenv-linter.readthedocs.io/
## Source
- [Agent Skill Exchange](https://agentskillexchange.com/skills/lint-dotenv-files-for-duplicated-keys-and-unsafe-formatting-with-dotenv-linter/)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!