Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Compare two versions of an OpenClaw skill to detect security-relevant changes. Use before updating any skill from ClawHub. Highlights new capabilities, chang...
Compare two versions of an OpenClaw skill to detect security-relevant changes. Use before updating any skill from ClawHub. Highlights new capabilities, chang...
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.
Compare two versions of an OpenClaw skill to find security-relevant changes before updating.
A skill that was clean at v1.0 could add credential stealing in v1.1. The skill scanner catches known bad patterns in a single version. The differ catches new capabilities between versions — things a skill couldn't do before but can do now.
python3 {baseDir}/scripts/differ.py diff --old ~/.openclaw/skills/some-skill/ --new /tmp/some-skill-v2/
python3 {baseDir}/scripts/differ.py diff --old ./v1/ --new ./v2/ --json
python3 {baseDir}/scripts/differ.py diff --old ./v1/ --new ./v2/ --summary
Network access (skill didn't make HTTP requests before, now it does) Credential access (didn't read env vars or API keys before, now it does) File system access (wasn't touching home directory, now it is) Code execution patterns (eval/exec that didn't exist before) Data exfiltration (new outbound POST requests) Obfuscation (new encoded/obfuscated content)
New files added (especially in scripts/) Deleted files (could remove safety checks) Modified files with security-relevant diffs
SAFE — No new security-relevant capabilities. Update freely. REVIEW — New capabilities detected. Read the changes before updating. BLOCK — Critical new capabilities (code execution, credential access). Manual audit required.
Always diff before updating any third-party skill Pair with skill-scanner: scan before first install, diff before every update Pay attention to new files — attackers add payloads in new scripts If a "bug fix" update adds network access, that's suspicious
Long-tail utilities that do not fit the current primary taxonomy cleanly.
Largest current source with strong distribution and engagement signals.