Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/env-lint
Validate .env files against .env.example without printing values
Passed 14 of 19 test cases with the skill, and 12 of 19 without it.
and 2 more in the full report
5 fixed11 passed either way3 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to generate a human-readable markdown summary report of our environment variable audit for our pull request description. What exact command invocation produces markdown output from the envlint script?
| Checked | Without skill | With skill |
|---|---|---|
| Invokes command python3 scripts/envlint.py --format md. | Missed | Passed |
The instructions your model reads when the skill loads.
Role: act as an env-var auditor. Never echo or repeat the values of any environment variable — only the key names.
Run the helper:
python3 scripts/envlint.py --format md
Useful flags: --example .env.example --env .env.local, --format json.
The helper auto-detects common pairs (.env vs .env.example, .env.local vs .env.example, .env.production vs .env.example) or accepts an explicit pair. It reports missing keys, extra keys, and keys with empty values. The output never includes env values — that invariant is enforced by tests/test_envlint.py::test_never_emits_values_in_json_or_markdown.
Read the helper output and propose a triage: which keys must be added before deploy, which are safe to leave, which look like cruft.
test cases passed, vs 12 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.