Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Comprehensive security auditing for Clawdbot deployments. Scans for exposed credentials, open ports, weak configs, and vulnerabilities. Auto-fix mode included.
Comprehensive security auditing for Clawdbot deployments. Scans for exposed credentials, open ports, weak configs, and vulnerabilities. Auto-fix mode included.
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.
Run a security audit to identify vulnerabilities in your Clawdbot setup before deployment or on a schedule. Use auto-fix to remediate common issues automatically.
No external dependencies required. Uses native system tools where available.
node skills/security-audit/scripts/audit.cjs
node skills/security-audit/scripts/audit.cjs --full
node skills/security-audit/scripts/audit.cjs --fix
node skills/security-audit/scripts/audit.cjs --credentials # Check for exposed API keys node skills/security-audit/scripts/audit.cjs --ports # Scan for open ports node skills/security-audit/scripts/audit.cjs --configs # Validate configuration node skills/security-audit/scripts/audit.cjs --permissions # Check file permissions node skills/security-audit/scripts/audit.cjs --docker # Docker security checks
node skills/security-audit/scripts/audit.cjs --full --json > audit-report.json
The audit produces a report with: LevelDescription🔴 CRITICALImmediate action required (exposed credentials)🟠 HIGHSignificant risk, fix soon🟡 MEDIUMModerate concern🟢 INFOFYI, no action needed
API keys in environment files Tokens in command history Hardcoded secrets in code Weak password patterns
Unexpected open ports Services exposed to internet Missing firewall rules
Missing rate limiting Disabled authentication Default credentials Open CORS policies
World-readable files Executable by anyone Sensitive files in public dirs
Privileged containers Missing resource limits Root user in container
The --fix option automatically: Sets restrictive file permissions (600 on .env) Secures sensitive configuration files Creates .gitignore if missing Enables basic security headers
security-monitor - Real-time monitoring (available separately)
Long-tail utilities that do not fit the current primary taxonomy cleanly.
Largest current source with strong distribution and engagement signals.