Zero Trust
v1.0.0Security-first behavioral guidelines for cautious agent operation. Use this skill for ALL operations involving external resources, installations, credentials, or actions with external effects. Triggers on - any URL/link interaction, package installations, API key handling, sending emails/messages, social media posts, financial transactions, or any action that could expose data or have irreversible effects.
⭐ 12· 5.3k·20 current·23 all-time
by@doonot
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill's name and description (a conservative security checklist) match the SKILL.md instructions. It requests no env vars, binaries, or installs that would be unrelated to a 'zero trust' policy.
Instruction Scope
The runtime instructions are appropriately restrictive and focused on verifying external interactions. Minor issues: the guidance hardcodes asking approval from a person named 'Pat' (unclear who that maps to in your workflow), and some items are prescriptive/opinionated (e.g., always store credentials under ~/.config/). The instructions could produce many human approval prompts, which may materially slow or block agent operations.
Install Mechanism
No install spec and no code files — lowest-risk form. Nothing is downloaded or written to disk by the skill itself.
Credentials
The skill requests no environment variables, credentials, or config paths beyond general storage recommendations. There is no disproportionate access requested.
Persistence & Privilege
The skill is not force-included (always:false) and is user-invocable. It does not request system-wide changes or modify other skills' configs.
Assessment
This skill is essentially a conservative checklist and is internally coherent and low-risk because it has no install or credential requirements. Before enabling it: (1) confirm who the skill means by the human approver ('Pat') and how human approvals will be presented to you, (2) be aware it will demand many explicit approvals and could slow automated workflows, (3) review/personalize prescriptive items (credential storage path, what counts as 'trusted' search engines), and (4) test it in a controlled environment to ensure its prompts and STOP/ASK guidance integrate with your agent's UI/workflow. If you need automatic operations, this skill's strictness may be impractical without human-in-the-loop tooling.Like a lobster shell, security has layers — review code before you run it.
latestvk9774ymzn14bzyh6gg2vymbh7980dq4v
License
MIT-0
Free to use, modify, and redistribute. No attribution required.