Privacy

v2.0.3

Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Privacy concepts, best practices, and implementation patterns.

0· 161·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description promise a privacy reference and the included files (SKILL.md and a small bash script) implement only static reference text. No unrelated credentials, binaries, or cloud access are requested.
Instruction Scope
SKILL.md and the script restrict output to heredoc text and state no network/API usage. Minor content inconsistencies exist: the quickstart text generically mentions "Required tools and access credentials" while the skill declares no required env vars/credentials; this appears to be documentation wording rather than an instruction to collect secrets.
Install Mechanism
No install spec is present and the skill is instruction-only with a bundled script. Nothing is downloaded or written to disk by an installer, so install risk is low.
Credentials
The skill declares no required environment variables, credentials, or config paths and the runtime script does not read environment variables or secrets. The requested environment access is proportionate (none) to the stated purpose.
Persistence & Privilege
always is false and the skill does not request permanent presence or modify other skills/config. It does not require elevated privileges or persistent background behavior.
Assessment
This skill appears to be a simple, local reference: it prints static privacy documentation and does not require credentials or network access. Before installing/running, you can: (1) inspect the included script (scripts/script.sh) yourself — it only outputs heredoc text; (2) note the small doc inconsistencies (version mismatch 2.0.3 vs 2.0.2 and wording about "access credentials" in quickstart) which are likely benign editorial issues; and (3) run it in a low-privilege or sandboxed environment if you prefer. There are no signs of data exfiltration or unexpected network calls.

Like a lobster shell, security has layers — review code before you run it.

latestvk976rmgrka24faavhxy0na7kw583gg33

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments