Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Security audit engine for OpenClaw configurations. Detects vulnerabilities, misconfigurations, secret leaks, and over-privileged agents. Use when the user as...
Security audit engine for OpenClaw configurations. Detects vulnerabilities, misconfigurations, secret leaks, and over-privileged agents. Use when the user as...
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 OpenClaw config for security vulnerabilities, misconfigurations, and best-practice violations. Produces a structured JSON report with risk scores, findings, and remediation steps.
User asks to check/audit/review their OpenClaw security User wants to harden their config before deploying User is setting up a new OpenClaw instance User asks about secret leakage or API key exposure in their config Before publishing or sharing any config file
node scripts/shield-audit.sh Or directly: node SKILL_DIR/bin/shield.js audit ~/.openclaw/openclaw.json --summary
Gateway Auth — missing/weak auth, insecure UI settings Network Exposure — bind address, Tailscale funnel, wildcard proxies Channel Security — wildcard allowFrom, missing allowlists DM Policy — open DM policy without pairing Subagent Permissions — wildcard allowAgents, circular delegation chains, self-delegation Tool Permissions — over-privileged agents with tools.profile: "full" Secret Leakage — API keys, tokens, private keys in plaintext config Sandbox/Execution — missing workspace isolation, no execution policies Plugin Config — enabled plugins without channel config Heartbeat Exposure — sensitive data in heartbeat prompts Remote Config — unencrypted WebSocket, exposed remote URLs/tokens
node SKILL_DIR/bin/shield.js audit <config.json> node SKILL_DIR/bin/shield.js audit <config.json> --summary # human-readable
cat config.json | node SKILL_DIR/bin/shield.js audit --stdin
node SKILL_DIR/bin/shield.js sanitize <config.json>
const { auditConfig } = require('SKILL_DIR/src/audit'); const config = require('./openclaw.json'); const report = auditConfig(config); console.log(report.risk_level); // "CRITICAL" | "HIGH" | "MEDIUM" | "LOW" console.log(report.overall_score); // 0-100 console.log(report.vulnerabilities); // detailed findings
Returns JSON with: risk_level, overall_score (0-100), vulnerabilities[], vulnerability_count, best_practices_compliance, action_recommended, safe_to_deploy, audit_timestamp.
Load the user's config: cat ~/.openclaw/openclaw.json Run: node SKILL_DIR/bin/shield.js audit ~/.openclaw/openclaw.json --summary Present findings to user with prioritized recommendations Offer to sanitize before sharing: node SKILL_DIR/bin/shield.js sanitize <file>
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.