Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Security gate for OpenClaw AgentSkills. Scans folder/ClawHub skills with cisco-ai-defense/skill-scanner before installation. Supports manual scans, staged in...
Security gate for OpenClaw AgentSkills. Scans folder/ClawHub skills with cisco-ai-defense/skill-scanner before installation. Supports manual scans, staged in...
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.
Harden OpenClawโs skill supply chain: Scan skills with cisco-ai-defense/skill-scanner Block only on High/Critical Allow Medium/Low/Info but warn Auto-scan on changes to ~/.openclaw/skills Quarantine failing skills to ~/.openclaw/skills-quarantine
cd "$HOME/.openclaw/workspace" # or wherever you keep repos git clone https://github.com/cisco-ai-defense/skill-scanner cd skill-scanner CC=gcc uv sync --all-extras Note: some environments try gcc-12 while building yara-python; forcing CC=gcc avoids that.
User skills live at: ~/.openclaw/skills Run: $HOME/.openclaw/skills/skill-scanner-guard/scripts/scan_openclaw_skills.sh Outputs go to: /home/rev/.openclaw/workspace/skill_scans/
Use the wrapper instead of copying directly: $HOME/.openclaw/skills/skill-scanner-guard/scripts/scan_and_add_skill.sh /path/to/skill-dir Policy: Block only if High/Critical exist (unless --force) Still installs if only Medium/Low/Info exist, but prints a warning summary
Install to a staging dir, scan, then copy into ~/.openclaw/skills only if allowed: $HOME/.openclaw/skills/skill-scanner-guard/scripts/clawhub_scan_install.sh <slug> # optionally $HOME/.openclaw/skills/skill-scanner-guard/scripts/clawhub_scan_install.sh <slug> --version <version>
Install the units (templates are in references/): mkdir -p ~/.config/systemd/user cp -a "$HOME/.openclaw/skills/skill-scanner-guard/references/openclaw-skill-scan."* ~/.config/systemd/user/ systemctl --user daemon-reload systemctl --user enable --now openclaw-skill-scan.path Behavior: Any change under ~/.openclaw/skills/ triggers scripts/auto_scan_user_skills.sh If High/Critical findings exist, the script moves failing skill directories to: ~/.openclaw/skills-quarantine/<skillname>-<timestamp> Reports are written to: /home/rev/.openclaw/workspace/skill_scans/auto/ Inspect: systemctl --user status openclaw-skill-scan.path journalctl --user -u openclaw-skill-scan.service -n 100 --no-pager ls -la ~/.openclaw/skills-quarantine
scan_openclaw_skills.sh: generate markdown reports for user + bundled skills scan_and_add_skill.sh: scan candidate folder skill; install only if allowed clawhub_scan_install.sh: stage-install from ClawHub, scan, then install auto_scan_user_skills.sh: scan-all on ~/.openclaw/skills changes; quarantine High/Critical failures
openclaw-skill-scan.path / openclaw-skill-scan.service: systemd --user path trigger units
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.