Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use Preloop's request_approval tool to get human approval before risky operations like deletions, production changes, or external modifications
Use Preloop's request_approval tool to get human approval before risky operations like deletions, production changes, or external modifications
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. Then review README.md for any prerequisites, environment setup, or post-install checks. 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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Use Preloop's request_approval MCP tool to get human approval before executing risky operations. Preloop will notify the user (via Slack, email, mobile apps, etc.) and wait for their response.
Preloop must be configured as an MCP server. See references/SETUP.md for configuration details.
Deleting anything (files, directories, database records, cloud resources) Production changes (deployments, config changes, environment variables) Database operations (schema changes, migrations, bulk deletions/updates) External modifications (creating/merging PRs, posting to APIs, sending emails) Security changes (permissions, access controls, API keys) Financial operations (purchases, charges, refunds) System modifications (installing packages, changing system settings, CI/CD changes)
Creating pull requests or issues (unless explicitly requested) Pushing commits to main/master branches Modifying critical files (package.json, requirements.txt, docker-compose.yml, etc.) Running commands that modify system state Making bulk changes (affecting many files/records)
Reading files or data Searching or querying Creating feature branches Running tests (in isolated environments) Making commits to feature branches
Call the request_approval tool BEFORE executing the risky operation.
Required: operation (string): Clear, specific description of what you'll do โ Good: "Delete the logs/2024-01/ directory containing 1,234 log files (2.3GB)" โ Bad: "Delete some logs" context (string): Additional details about what will be affected โ Good: "This directory contains archived application logs from January 2024. The logs have been backed up to S3. Deleting will free up 2.3GB." โ Bad: "Old logs" reasoning (string): Why this operation is necessary โ Good: "Disk usage is at 92% capacity. These logs are archived in S3 and no longer needed locally." โ Bad: "Need more space" Optional: caller (string): Auto-populated by Preloop approval_policy (string): Specific approval policy name (uses account default if omitted)
The tool returns a string: Approved: Success message โ proceed with the operation Denied: "Approval denied" or "Approval denied: {reason}" โ STOP, don't execute Error: Error message โ check configuration or try again
Task: User asks to delete old cache files Your workflow: Check what exists: 3,421 cache files, 1.8GB, from last week Call request_approval: operation: "Delete the temp-cache/ directory" context: "Contains 3,421 cache files totaling 1.8GB from batch jobs that ran last week. All jobs completed successfully." reasoning: "Cache is no longer needed and is consuming disk space. Results are in the database." Wait for response If "denied" in response โ tell user it's cancelled, ask for alternatives If approved โ proceed with deletion See references/EXAMPLES.md for more examples.
When unsure: Can this be undone easily? NO โ Request approval Could this cause harm or data loss? YES โ Request approval Is this modifying production or external systems? YES โ Request approval Would a human want to review this first? YES โ Request approval Am I uncertain about the safety? YES โ Request approval Golden Rule: When in doubt, request approval. Better to ask unnecessarily than to cause harm.
Stop immediately - do NOT proceed Check for comments - denial may include reasoning Inform the user - explain why it was cancelled Look for alternatives - can you accomplish the goal differently? Don't retry - don't ask again unless circumstances change
DO: โ Request approval BEFORE executing โ Be specific and detailed โ Include numbers (file count, size, affected records) โ Explain the impact โ Respect denials DON'T: โ Execute first, then ask โ Be vague โ Bundle multiple operations โ Proceed if denied โ Skip approval because you think it's "probably fine"
references/SETUP.md - Configuration and MCP server setup references/EXAMPLES.md - Detailed examples and workflows references/TROUBLESHOOTING.md - Common errors and solutions Remember: Safety first! Trust is earned by being cautious and respectful of the user's systems and data.
Long-tail utilities that do not fit the current primary taxonomy cleanly.
Largest current source with strong distribution and engagement signals.