Skill Vetting

v1.1.0

Vet ClawHub skills for security and utility before installation. Use when considering installing a ClawHub skill, evaluating third-party code, or assessing w...

7· 13.2k·229 current·243 all-time
byEddy@eddygk
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description match implementation: the package contains a scanner (scripts/scan.py), pattern references, and a SKILL.md workflow that instructs downloading a skill zip and scanning it. No unexpected env vars or binaries are requested. Requiring no external credentials and including a local scanner is proportionate to the stated vetting purpose.
Instruction Scope
SKILL.md instructs the agent to download target skills into /tmp, run the included scanner, and manually inspect flagged files — all within the vetting scope. SKILL.md also contains explicit guidance addressing AI reviewers and immutable rules for not following in-file instructions; those lines match prompt-injection detection heuristics (pre-scan found 'ignore-previous-instructions'). This is expected for a vetting tool (it intentionally exemplifies and warns about injection), but it means you must ensure the vetting workflow itself (and any automated decisions) remain conservative and human-reviewed.
Install Mechanism
No install spec (instruction-only) and the only code is the included scanner and documentation. That is low-risk compared with remote installers. The workflow directs users to download target skills from the ClawHub API (https://clawhub.ai/api/v1/download?slug=...), which is consistent with the tool's purpose; downloading and unzipping third-party zips is inherently risky but is the intended operation of a vetting tool and is mitigated by instructing use of /tmp and manual review.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. The scanner inspects files and uses regex patterns only; that level of access matches the vetting purpose and is appropriately minimal.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent presence or modify other skills. Autonomous invocation is allowed (platform default) but not raised by this skill's metadata. No elevated privileges are requested.
Scan Findings in Context
[prompt-injection:ignore-previous-instructions] expected: The pre-scan flagged phrases like 'ignore previous instructions' in SKILL.md. This SKILL intentionally documents and demonstrates prompt-injection strings to teach detection and to instruct reviewers not to obey in-file directives, so this pattern is expected for the vetting tool.
[scanner.patterns.prompt_injection] expected: scripts/scan.py contains regexes that detect social-engineering/prompt-injection patterns (e.g., patterns matching 'AI', 'assistant', 'ignore', invisible unicode). That is intended behavior for a security scanner and appropriate for the skill.
[scanner.patterns.code_execution_and_network_checks] expected: The scanner contains many rules for eval/exec, subprocess shell=True, base64 decoding, network calls, and file ops. Those detections are expected because the scanner's job is to flag exactly those constructs in target skills.
Assessment
This skill appears to be what it claims: a local vetting tool that ships a regex-based scanner and an explicit review workflow. Pay attention to these points before using it to auto-approve skills: - Treat the scanner output as advisory: the script uses regex rules (documented in references) and can produce false positives and false negatives; always manually inspect flagged lines in context. - The SKILL.md contains text that will match prompt-injection detectors; this is intentional here (the skill demonstrates and warns about such patterns). Do not assume that pattern-matching text in a reviewed third-party skill is benign — use the same conservative rules the SKILL.md recommends. - Run the scanner and manual review in an isolated/sandboxed environment (/tmp as suggested) and avoid executing untrusted code. Do not run any downloaded skill code unless you fully inspected it or executed it in a disposable/containerized environment. - If the scanner flags prompt_injection with CRITICAL severity in a target skill, follow the skill's own hard rule: reject and escalate for human review — do not attempt to 'downgrade' findings based on in-file comments. - Because the scanner is regex-based, consider augmenting with manual semantic review for time-delayed or obfuscated behaviors. If you need higher assurance, run the later-phase mediator/consensus approach described in ARCHITECTURE.md. Overall: safe and coherent for vetting work, but keep human-in-the-loop and sandbox downloaded artifacts.

Like a lobster shell, security has layers — review code before you run it.

latestvk97130pmfb7vrctxfxrga49snd818cn0

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments