New to Claude Skills? Learn how to install them โ†’

netease-youdao on GitHub

Skill Vetter

Free

Ensure safety before installing AI skills.

Get this skill

Free ยท Opens the source repo

What Skill Vetter does

Skill Vetter is a security-focused tool designed to vet AI agent skills before installation. It is crucial for developers and designers who often work with various skills from platforms like ClawdHub and GitHub. The vetting process is thorough, consisting of multiple steps that help identify potential security risks associated with a skill. By following the outlined protocol, users can ensure that they do not inadvertently install malicious or poorly designed code that could compromise their systems.

The vetting protocol begins with a source check, where users assess the origin of the skill, the reputation of its author, and community feedback such as downloads and reviews. This initial step is vital for establishing trust in the skill's source. The next step involves a mandatory code review, where users must scrutinize the skill's code for any red flags, such as unauthorized network calls or requests for sensitive information. This step is crucial to prevent the execution of harmful code.

After the code review, users evaluate the skill's permission scope to determine what files it needs access to and whether those permissions are appropriate for its functionality. Finally, the skill is classified into a risk level, which helps users make informed decisions about whether to install it. The output of the vetting process is a comprehensive report that summarizes the findings and provides a clear verdict on the skill's safety.

Skill Vetter is ideal for anyone involved in deploying or using AI skills, especially in environments where security is paramount. It empowers users to make informed decisions and enhances the overall security posture of their AI agent ecosystem.

When to use it

Use Skill Vetter before installing any AI skill from third-party sources or when evaluating shared skills.

When not to use it

This tool may not be necessary for skills from trusted official sources where security is already assured.

What you can build with it

Vetting a New Skill from GitHub

Before installing a new skill from a GitHub repository, run Skill Vetter to assess its safety.

Evaluating Shared Skills

When receiving skills from other agents, use Skill Vetter to ensure they don't pose security risks.

Checking Permissions of Skills

Use Skill Vetter to analyze the permission scope of a skill before installation to avoid unnecessary risks.

How to install Skill Vetter

View source

1. Install with the skills CLI

npx skills add netease-youdao/lobsterai/skill-vetter --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by netease-youdao

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]
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. ๐Ÿ”’๐Ÿฆ€

Frequently asked questions about Skill Vetter

Similar skills