Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/varlock-claude-skill
Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits
Passed 17 of 22 test cases with the skill, and 16 of 22 without it.
2 fixed15 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
When building Docker images, developers sometimes pass secrets via `ENV` instructions in Dockerfiles or plain `.env` files mounted during `docker build`, exposing keys in image layers. What is the correct pattern for passing secrets during build and runtime safely without leaking keys in container metadata or history?
| Checked | Without skill | With skill |
|---|---|---|
| The response advises against using static `ENV` instructions in Dockerfiles for secret values. | Passed | Passed |
| The response recommends injecting environment variables at runtime. | Missed | Passed |
The instructions your model reads when the skill loads.
Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits
Use this skill when you need to work with secure environment variable management ensuring secrets are never exposed in claude sessions, terminals, logs, or git commits.
This skill provides guidance and patterns for secure environment variable management ensuring secrets are never exposed in claude sessions, terminals, logs, or git commits.
For more information, see the source repository.
test cases passed, vs 16 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.