Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Scan OpenClaw skill folders for security red flags before installing or publishing. Detects data exfiltration, credential theft, prompt injection, destructiv...
Scan OpenClaw skill folders for security red flags before installing or publishing. Detects data exfiltration, credential theft, prompt injection, destructiv...
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.
Security scanner for OpenClaw agent skills. Static analysis for red flags.
node scripts/scanner.js <path-to-skill> [--verbose] [--json] [--summary] [--ignore <path>] [--include-self]
# Scan a downloaded skill folder before enabling it clawhub inspect some-skill node scripts/scanner.js ./skills/some-skill --verbose # Scan your own skill before publishing node scripts/scanner.js ./skills/my-skill # JSON output for automation node scripts/scanner.js ./skills/my-skill --json # One-line summary output for heartbeat checks node scripts/scanner.js ./skills/my-skill --summary # Include scanner internals (off by default to reduce self-scan noise) node scripts/scanner.js ./skills/skulk-skill-scanner --include-self
SeverityFlags🔴 CriticalData exfiltration, credential access, safety overrides, destructive commands🟠 HighObfuscation (base64/eval), unknown network access, env scanning, privilege escalation, hidden instructions🟡 MediumWrites outside workspace, package installs (supply chain), messaging on user's behalf, persistent timers/automation🔵 InfoAPI key references, broad tool access requests
Each unique rule deducts points: critical=30, high=15, medium=5, info=0 Score 75-100: ✅ PASS Score 50-74: ⚠️ WARN Score 0-49 or any critical: ❌ FAIL Exit code 1 on FAIL (CI-friendly)
Known legitimate API domains are allowlisted to reduce false positives on network-related rules. Edit the SAFE_DOMAINS array in scripts/scanner.js to customize.
This is static pattern matching — it catches obvious and moderately obfuscated attacks but cannot detect: Sophisticated multi-step social engineering Runtime-generated URLs or dynamic exfiltration Attacks that look identical to legitimate skill behavior It's a first line of defense, not a guarantee. Always review skills manually before granting sensitive access.
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.