skill-vetter — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited skill-vetter (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Skill Vetter — ClawHub
Security-first vetting protocol for AI agent skills. Never install a skill without vetting it first.
When to Use
Vetting Protocol
Step 1: Source Check Questions to answer:
Step 2: Code Review (MANDATORY) Read ALL files in the skill. Check for these RED FLAGS:
🚨 REJECT IMMEDIATELY IF YOU SEE: ───────────────────────────────────────── • curl/wget to unknown URLs • Sends data to external servers • Requests credentials/tokens/API keys • Reads ~/.ssh, ~/.aws, ~/.config without clear reason • Accesses MEMORY.md, USER.md, SOUL.md, IDENTITY.md • Uses base64 decode on anything • Uses eval() or exec() with external input • Modifies system files outside workspace • Installs packages without listing them • Network calls to IPs instead of domains • Obfuscated code (compressed, encoded, minified) • Requests elevated/sudo permissions • Accesses browser cookies/sessions • Touches credential files ─────────────────────────────────────────
Step 3: Permission Scope Evaluate:
Step 4: Risk Classification
Risk Level | Examples | Action 🟢 LOW | Notes, weather, formatting | Basic review, install OK 🟡 MEDIUM | File ops, browser, APIs | Full code review required 🔴 HIGH | Credentials, trading, system | Human approval required ⛔ EXTREME | Security configs, root access | Do NOT install
Output Format After vetting, produce this report:
SKILL VETTING REPORT ═══════════════════════════════════════ Skill: [name] Source: [ClawdHub / GitHub / other] Author: [username] Version: [version] ─────────────────────────────────────── METRICS: • Downloads/Stars: [count] • Last Updated: [date] • Files Reviewed: [count] ─────────────────────────────────────── RED FLAGS: [None / List them]
PERMISSIONS NEEDED: • Files: [list or "None"] • Network: [list or "None"] • Commands: [list or "None"] ─────────────────────────────────────── RISK LEVEL: [🟢 LOW / 🟡 MEDIUM / 🔴 HIGH / ⛔ EXTREME]
VERDICT: [✅ SAFE TO INSTALL / ⚠️ INSTALL WITH CAUTION / ❌ DO NOT INSTALL]
NOTES: [Any observations] ═══════════════════════════════════════
Quick Vet Commands For GitHub-hosted skills:
curl -s "https://api.github.com/repos/OWNER/REPO" | jq '{stars: .stargazers_count, forks: .forks_count, updated: .updated_at}'
curl -s "https://api.github.com/repos/OWNER/REPO/contents/skills/SKILL_NAME" | jq '.[].name'
curl -s "https://raw.githubusercontent.com/OWNER/REPO/main/skills/SKILL_NAME/SKILL.md"
Trust Hierarchy
Official OpenClaw skills → Lower scrutiny (still review) High-star repos (1000+) → Moderate scrutiny Known authors → Moderate scrutiny New/unknown sources → Maximum scrutiny Skills requesting credentials → Human approval always
Remember
Paranoia is a feature. 🔒🦀
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.