Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Enforces guarded execution with safe_exec, safe_send, and safe_action. Use when a task may run shell commands, send channel messages, or call external APIs/a...
Enforces guarded execution with safe_exec, safe_send, and safe_action. Use when a task may run shell commands, send channel messages, or call external APIs/a...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Apply this skill whenever a request can: execute shell/system commands; send outbound messages/posts to channels; trigger external actions (email, DB, gateways, automation).
Use safe_exec instead of raw exec. Use safe_send instead of direct channel-post tools. Use safe_action for generic external/API side effects. Never bypass the guardrails resolver with direct destructive tools. If decision is require_approval, stop and wait for explicit approval flow.
Always provide the narrowest cwd for safe_exec. Include sender/channel/agent context when available. Keep command args explicit; do not hide risky flags in shell expansions. For safe_action, include explicit resources where possible.
Use for shell commands only after permission resolution. Expected input shape: { "command": "git", "args": ["status"], "cwd": "/workspace/project" }
Use for outbound channel messages. Expected input shape: { "channel": "telegram:ops-room", "message": "Deployment done", "channelType": "telegram" }
Use for side-effect actions that are not plain shell or plain chat send. Expected input shape: { "action": "gmail.delete_message", "payload": { "messageId": "..." }, "resources": [ { "kind": "unknown", "value": "email-api", "operation": "delete" } ] }
allow: continue and return runtime result. deny: return denial with reason code; do not retry with alternate dangerous tools. require_approval: surface approval id/reason and wait for /approve <id> or RPC approval.
Prefer read-only commands (git status, rg, ls) before mutable ones. Propose reversible operations first. Ask for confirmation before destructive intent, even if technically allowed.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.