Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Audit a ClawHub skill for security risks BEFORE installation. Use when: (1) user is about to install a ClawHub skill, (2) user asks if a skill is safe, (3) r...
Audit a ClawHub skill for security risks BEFORE installation. Use when: (1) user is about to install a ClawHub skill, (2) user asks if a skill is safe, (3) r...
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.
Audit any ClawHub skill for security risks before installation.
Tell OpenClaw: "Install the skill-trust-auditor skill." The agent will handle the installation and configuration automatically.
If you prefer the terminal, run: clawhub install skill-trust-auditor
bash scripts/setup.sh
When user says "audit [skill-name]" or "is [skill-name] safe" or before any clawhub install: bash scripts/audit.sh [skill-name-or-url] # Example: bash scripts/audit.sh steipete/clawhub bash scripts/audit.sh https://clawhub.ai/someuser/someskill Output: { "skill": "someuser/someskill", "trust_score": 72, "verdict": "INSTALL WITH CAUTION", "risks": [ {"level": "HIGH", "pattern": "curl to external domain", "location": "scripts/sync.sh:14"}, {"level": "MEDIUM", "pattern": "reads MEMORY.md", "location": "SKILL.md:23"} ], "safe_patterns": ["no env var access", "no self-modification"], "author_verified": false, "recommendation": "Review scripts/sync.sh:14 before installing. The external curl call could exfiltrate data." } Post to user with clear summary: ๐ก๏ธ Trust Audit: someuser/someskill Score: 72/100 โ โ ๏ธ INSTALL WITH CAUTION ๐ด HIGH: curl to unknown domain in scripts/sync.sh:14 ๐ก MEDIUM: reads your MEMORY.md Recommendation: Inspect line 14 of sync.sh before proceeding. Run: clawhub show someuser/someskill --file scripts/sync.sh
ScoreVerdictAction90-100โ SAFEInstall freely70-89โ ๏ธ CAUTIONReview flagged items first50-69๐ RISKYOnly if you understand the risks0-49๐ด DO NOT INSTALLHigh probability of malicious intent
HIGH RISK (-30 each): process.env access in scripts curl/wget to non-standard domains Reading ~/.config or ~/.openclaw directly exec() with user-controlled input Instructions to modify SOUL.md/AGENTS.md/openclaw.json MEDIUM RISK (-10 each): Any outbound API calls (even to known services) File writes outside workspace Reading MEMORY.md or diary files LOW RISK (-3 each): web_fetch to standard domains Read-only file access in workspace
Optionally prepend audit to every install: # Add to your shell aliases: alias clawhub-safe='bash ~/.openclaw/workspace/skills/skill-trust-auditor/scripts/audit.sh $1 && clawhub install $1'
See references/clawhavoc-patterns.md for known malicious patterns from the February 2026 incident. Update this file when new incidents are reported.
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.