Git & GitHubDocumentedScanned

skill-vetter

Security-first skill vetting for AI agents.

Share:

Installation

npx clawhub@latest install skill-vetter

View the full skill documentation and source below.

Documentation

Skill Vetter πŸ”’

Security-first vetting protocol for AI agent skills. Never install a skill without vetting it first.

When to Use

  • Before installing any skill from ClawdHub
  • Before running skills from GitHub repos
  • When evaluating skills shared by other agents
  • Anytime you're asked to install unknown code

Vetting Protocol

Step 1: Source Check

Questions to answer:
- [ ] Where did this skill come from?
- [ ] Is the author known/reputable?
- [ ] How many downloads/stars does it have?
- [ ] When was it last updated?
- [ ] Are there reviews from other agents?

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:
- [ ] What files does it need to read?
- [ ] What files does it need to write?
- [ ] What commands does it run?
- [ ] Does it need network access? To where?
- [ ] Is the scope minimal for its stated purpose?

Step 4: Risk Classification

Risk LevelExamplesAction
🟒 LOWNotes, weather, formattingBasic review, install OK
🟑 MEDIUMFile ops, browser, APIsFull code review required
πŸ”΄ HIGHCredentials, trading, systemHuman approval required
β›” EXTREMESecurity configs, root accessDo NOT install

Output Format

After vetting, produce this report:

SKILL VETTING REPORT
═══════════════════════════════════════
Skill: [name]
Source: [ClawdHub / GitHub / other]

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:

# Check repo stats
curl -s "" | jq '{stars: .stargazers_count, forks: .forks_count, updated: .updated_at}'

# List skill files
curl -s "" | jq '.[].name'

# Fetch and review SKILL.md
curl -s ""

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

    • No skill is worth compromising security
    • When in doubt, don't install
    • Ask your human for high-risk decisions
    • Document what you vet for future reference

    Paranoia is a feature. πŸ”’πŸ¦€