OpenClaw only
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
- Security
- Version 1.0.0
The facts
- Publisher
- spclaudehome
- Runs on
- OpenClaw only
- Updated
- September 16, 2026
- Downloads on ClawHub
- 274.6k
- Installs on ClawHub
- 12.2k
- Stars
- 1.3k
- Category
- Security View on ClawHub
Security review
This skill is a security checklist for reviewing other skills and does not contain hidden execution, persistence, credential use, or destructive behavior.
The review is ClawHubβs, shown here as published. Diali does not edit it. Read the full audit on ClawHub
What it needs before the first run
Nothing to configure. It runs as soon as it is installed.
Install it on your Diali agent
Open Skills in the dashboard
Every plan includes the catalog. Search for the skill by name.
Read the review, then install
The verdict and summary above are shown again on the install screen. Pick the agent it goes on.
Give it what it needs, then use it
If the skill asks for credentials or settings, the dashboard collects them. The skill then runs inside the agentβs own sandbox.
From the skillβs README
Written by the publisher and shown as published on ClawHub.
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 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:
# Check repo stats
curl -s "https://api.github.com/repos/OWNER/REPO" | jq '{stars: .stargazers_count, forks: .forks_count, updated: .updated_at}'
# List skill files
curl -s "https://api.github.com/repos/OWNER/REPO/contents/skills/SKILL_NAME" | jq '.[].name'
# Fetch and review SKILL.md
curl -s "https://raw.githubusercontent.com/OWNER/REPO/main/skills/SKILL_NAME/SKILL.md"Trust Hierarchy
1. Official OpenClaw skills β Lower scrutiny (still review) 2. High-star repos (1000+) β Moderate scrutiny 3. Known authors β Moderate scrutiny 4. New/unknown sources β Maximum scrutiny 5. 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.* ππ¦
Give a skill an agent to run on
Every plan includes the skills catalog, every channel and every connector. Build an agent and install your first skill from the dashboard.
