SKILLEMALL.ai
GitHub ↗ RU Sign in

AB Env Doctor

Scans your codebase to auto-discover every environment variable referenced in source code, generates a fully-documented .env.example, detects missing vars in your current .env, and flags security risks (logged secrets, committed .env files, exposed keys). Works across Node.js, Python, Go, Ruby, and shell scripts. Zero config — just run it in your project directory. Triggers on "env doctor", "check env vars", "generate .env.example", "missing environment variables", "audit secrets", "/env-doctor".

ClawHub Agent Skills author: Lucius Pang v1.0.3 MIT-0 2 files body ≈ 2 092 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 66/100 · Nearly there — weak spots: inputs and preconditions, consistency, running it twice

ReferenceSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
B
66/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 66/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 3 mutating operations with no state check
  • 40Consistency. Frontmatter name (Env Doctor) differs from the folder (phy-env-doctor)
  • 55Failures and branches. 1 branches
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 100Tools and files. No external tools needed
  • 100Steps. 22 steps
  • 100Execution cost. Instruction body is 2092 tokens
  • low 10 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +2Single-language instructions
  • +5Description quotes 6 example trigger phrases
  • +3Description length 501: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 22 items
  • +3Output format is stated explicitly
  • +4Has examples (7 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.

External checks

ClawHub: clean
Env Doctor is a local repository auditing skill whose file reads and generated example file match its stated environment-variable documentation and secret-checking purpose.
LLM: benign (high) · VirusTotal: · 29 May 2026