humanenv-usage
Skill53 starsChanged 5 months agoMITView on GitHub
Use humanenv to retrieve sensitives/envs. Never log/read sensitives from humanenv. They are envs for humans only.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cavemanSkill
- context-modeSkill
- diagnoseSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- prototypeSkill
- setup-matt-pocock-skillsSkill
- supercli-docs-devSkill
- supercli-masterySkill
- supercli-mcp-devSkill
- tddSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- write-a-skillSkill
- zoom-outSkill
- playwright-cliSkill
- supercli.quickstartSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
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 9
Use humanenv.get('key') inside your application.
- Distinctive: line 12
Use humanenv CLI to retrieve envs.
- Distinctive: line 15
NEVER log env values retrieved from humanenv
- Distinctive: line 16
NEVER dump or export multiple values at once
- Distinctive: line 17
ALWAYS null variables after use
- Distinctive: line 18
NEVER write sensitives to files
- Distinctive: line 19
Do not generate scripts that use humanenv in loops or to exfiltrate data
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
How to retrieve sensitives
JavaScript API
Use humanenv.get('key') inside your application. The returned value must be used immediately and then set to null to prevent memory leaks.
CLI
Use humanenv CLI to retrieve envs. Do not attempt to log or dump all envs.
Rules
- NEVER log env values retrieved from humanenv
- NEVER dump or export multiple values at once
- ALWAYS null variables after use
- NEVER write sensitives to files
- Do not generate scripts that use humanenv in loops or to exfiltrate data
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.

