Privacy Shield
v1.0.1Manages sensitive data access by marking resources with privacy levels and enforcing share, export, and usage restrictions based on a centralized registry.
⭐ 0· 98·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (privacy marking, enforcement, and audit) matches the included CLI script and SKILL.md instructions. No unrelated environment variables, binaries, or external services are required.
Instruction Scope
SKILL.md instructs agents to run the included script before any data-output operation; the script reads/writes local files (data/privacy-registry.json and data/privacy-audit.jsonl) under the WORKSPACE (or repo-root) — this is expected for the stated purpose but means the agent will access and modify workspace files and create audit logs.
Install Mechanism
No install spec or external downloads are present; the skill is instruction-only with a bundled Python script. No network installs or archive extraction are used.
Credentials
The skill does not require credentials or extra environment variables. It optionally respects WORKSPACE to locate registry/audit files, which is reasonable for a local file-based tool.
Persistence & Privilege
always is false and the skill does not request persistent platform privileges. It will read/write its own registry and audit files only; nothing in the code modifies other skills or system-wide settings.
Assessment
This skill appears to do what it says: a local privacy registry and CLI that checks and logs decisions. Before installing or invoking it, consider: (1) it will read/write data/privacy-registry.json and data/privacy-audit.jsonl in the agent workspace (or the directory implied by WORKSPACE) — review and set appropriate file permissions; (2) confirm you are comfortable allowing the agent to execute the included Python script (it runs locally and does not contact external endpoints); (3) review registry contents and audit logs for sensitive items before sharing them with other tools or people; (4) if you set WORKSPACE, ensure it points to the intended workspace so the registry/audit files land where you expect. No credentials or network calls were found in the code.Like a lobster shell, security has layers — review code before you run it.
latestvk9730dc4v39f5jzj71qpf3jdd583801q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.