Cloak provides a security layer for environment variables, ensuring that AI coding agents only interact with fake 'sandbox' values while the human developer retains access to the real credentials via a secure vault and OS keychain integration.
Use this skill in any project where you want to prevent an LLM from accidentally reading, logging, or exfiltrating production secrets from .env files.
.cloak file, prohibits direct editing of protected .env files, and mandates the use of cloak run for executing processes that require real secrets.Claude Code, Cursor, Windsurf, and other AI coding agents that follow project-root instruction files (CLAUDE.md, .cursorrules).
Cloak is a skill for protecting .env secrets from AI coding agents by replacing on-disk values with sandbox fakes and providing a vault/CLI for real credential access. The SKILL.md is well-written with clear instructions, detection rules, and a command reference. Both bundled scripts failed in isolation — cross-compat-test.sh requires the extension/ directory context, and release.sh requires arguments plus a git repo. Security concern: SKILL.md includes `curl | sh` install instructions, which is a remote code execution pattern, though presented as user-facing rather than agent-autonomous.
The curl|sh pattern is instructional (for suggesting to developers) rather than something the agent executes autonomously, but still warrants the security deduction. The skill concept is genuinely useful and well-structured. Scripts are production-quality release tooling, not core skill functionality.