Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Fail-closed security auditing for OpenClaw/ClawHub skills & repos: trufflehog secrets scanning, semgrep SAST, prompt-injection/persistence signals, and supply-chain hygiene checks before enabling or installing.
Fail-closed security auditing for OpenClaw/ClawHub skills & repos: trufflehog secrets scanning, semgrep SAST, prompt-injection/persistence signals, and supply-chain hygiene checks before enabling or installing.
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.
A hostile-by-design, fail-closed audit workflow for codebases and OpenClaw/ClawHub skills. It does not try to answer โdoes this skill work?โ. It tries to answer: โcan this skill betray the system?โ
This skillโs scripts combine multiple layers: Secrets / credential leakage: trufflehog Static analysis: semgrep (auto rules) Hostile repo audit (custom): prompt-injection signals, persistence mechanisms, suspicious artifacts, dependency hygiene If any layer fails, the overall audit is FAIL.
From this skill folder (use bash so it works even if executable bits were not preserved by a zip download): bash scripts/run_audit_json.sh <path> Example: bash scripts/run_audit_json.sh . > /tmp/audit.json jq '.ok, .tools' /tmp/audit.json
Set the strictness level (default: standard): OPENCLAW_AUDIT_LEVEL=standard bash scripts/run_audit_json.sh <path> OPENCLAW_AUDIT_LEVEL=strict bash scripts/run_audit_json.sh <path> OPENCLAW_AUDIT_LEVEL=paranoid bash scripts/run_audit_json.sh <path> standard: pragmatic strict defaults (lockfiles required; install hooks/persistence/prompt-injection signals fail) strict: more patterns become hard FAIL (e.g. minified/obfuscation artifacts) paranoid: no "best-effort" hashing failures; more fail-closed behavior
For strict/quarantine workflows, require a machine-readable intent/permissions manifest at repo root: openclaw-skill.json If a repo/skill does not provide this manifest, the hostile audit should treat it as FAIL. See: docs/OPENCLAW_SKILL_MANIFEST_SCHEMA.md.
Docker is optional here. This skill can be used for static auditing without Docker. If you want to execute any generated/untrusted code, run it in a separate sandbox workflow (recommended).
scripts/run_audit_json.sh โ main JSON audit runner scripts/hostile_audit.py โ prompt-injection/persistence/dependency hygiene scanner scripts/security_audit.sh โ convenience wrapper (always returns JSON, never non-zero) openclaw-skill.json โ machine-readable intent/permissions manifest
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.