env-doctor
Skill14 starsChanged 6 months agoMITView on GitHub
Diagnose your .env file before deployment. Catches the configuration bugs that only show up in production at 2 AM. The classic: ANTHROPIC_API_KEY=sk-ant-XXXX — copied from docs, never replaced The silent fail: DATABASE_URL= — trailing space means the var is a single space, not empty. Some parsers treat this as set. The Windows trap: .env edited on Windows has \r\n line endings. Some Node.js dotenv parsers include the \r in the value. "mypassword\r" is not "mypassword". The gitignore miss: .env.production not…
- Reads credentials
9 other projects use a version of this.
Adopted by
Most recently taken up by
- adithyanraj03/dsh-skills-packtheir own version, first seen Nov 15, 2026
- binay-py/claude-skillstheir own version, first seen Nov 15, 2026
- taxueseek/session-diggertheir own version, first seen Nov 14, 2026
- linxule/carreltheir own version, first seen Nov 8, 2026
- venhdev/skillstheir own version, first seen Nov 1, 2026
- sharklandy/claude-code-starter-kittheir own version, first seen Oct 20, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- taxueseek/session-digger★ 34same name
- unreadlogs/node-agent-skills★ 4same name
- linxule/carrel★ 2same name
- binay-py/claude-skills★ 1same name
- venhdev/skills★ 1same name
- abigayleh/claude-workflow-plugin★ 0same name
- adithyanraj03/dsh-skills-pack★ 0same name
- angelgabrieljacintohuayllasco/clipboard-skills★ 0same name
- sharklandy/claude-code-starter-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- llms.txtllms.txt
- claude-cost-trackerSkill
- commit-roastSkill
- context-budgetSkill
- debug-trailSkill
- ev-calculatorSkill
- git-standupSkill
- growth-trackerSkill
- investment-briefing-agentSkill
- multi-agent-orchestratorSkill
- news-sentiment-engineSkill
- options-flow-analyzerSkill
- price-monitor-alertSkill
- pr-review-prepSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 93
Read tool access (reads .env and .env.example)
- Distinctive: line 94
No API keys needed — pure text analysis
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Env Doctor
Diagnose your .env file before deployment. Catches the configuration bugs that only show up in production at 2 AM.
What it does
- Compares
.envagainst.env.example— finds missing vars - Detects placeholder values never replaced (
...,your-key-here,sk-ant-XXXX) - Flags secrets that look wrong (wrong prefix, wrong length, wrong format)
- Checks for common mistakes: trailing spaces, Windows line endings, BOM markers
- Warns about vars that exist in
.envbut not in.env.example(undocumented secrets) - Validates known API key formats (Anthropic, OpenAI, Stripe, Polygon, Telegram)
Usage
Run env doctor on this project.
Compare .env against .env.example.
Check for: missing vars, placeholder values, format issues, undocumented secrets.Example Output
Env Doctor — 2026-05-13
MISSING VARS (in .env.example but not in .env)
POLYGON_API_KEY — required for options scanner
NAVER_CLIENT_SECRET — required for Korean news feed
PLACEHOLDER VALUES (never replaced)
TWITTER_BEARER_TOKEN = "..." — still default
TWITTER_API_KEY = "..." — still default
FORMAT WARNINGS
ANTHROPIC_API_KEY = "sk-ant-api03-..."
OK: correct prefix, length looks right
TELEGRAM_BOT_TOKEN = "1234567890:ABC..."
OK: correct format (number:hash)
POLYGON_API_KEY = ""
WARN: empty string — key exists but has no value
UNDOCUMENTED SECRETS (in .env but not in .env.example)
DEVTO_API_KEY — consider adding to .env.example with placeholder
ENCODING ISSUES
None found (UTF-8, Unix line endings)
SUMMARY
2 missing required vars
2 placeholder vars not replaced
1 undocumented secret
0 encoding issues
Run: cp .env.example .env.local and fill in missing valuesValidated API key formats
| Service | Expected format | Example |
| Anthropic | sk-ant-api03-... | 50+ chars |
| OpenAI | sk-proj-... or sk-... | 51 chars |
| Stripe | sk_live_... or sk_test_... | 32+ chars |
| Polygon.io | alphanumeric, 32 chars | |
| Telegram Bot | {number}:{hash} | 1234567890:ABC... |
| dev.to | alphanumeric, 20 chars |
Configuration
Run env doctor:
Files: .env vs .env.example
Check format: ANTHROPIC_API_KEY, TELEGRAM_BOT_TOKEN, POLYGON_API_KEY
Required vars: ANTHROPIC_API_KEY, TELEGRAM_BOT_TOKEN, TELEGRAM_CHANNEL_ID
Warn if any var contains: "...", "your-", "xxx", "test", "placeholder"Common catches
The classic: ANTHROPIC_API_KEY=sk-ant-XXXX — copied from docs, never replaced
The silent fail: DATABASE_URL= — trailing space means the var is a single space, not empty. Some parsers treat this as set.
The Windows trap: .env edited on Windows has \r\n line endings. Some Node.js dotenv parsers include the \r in the value. "mypassword\r" is not "mypassword".
The gitignore miss: .env.production not in .gitignore. Happens when someone adds a new env file variant.
Requirements
- Read tool access (reads
.envand.env.example) - No API keys needed — pure text analysis
Free
Fully free and open source.
→ https://github.com/tellmefrankie/news-engine
Author
Built after a production deploy failed because TELEGRAM_BOT_TOKEN was still "..." in the production .env. The env doctor would have caught it in 2 seconds.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

