skills/skill-vetter/SKILL.md
Skill Vetter — ClawHub 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?
npx skillsauth add songsunny00/myskills skills/skill-vetterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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. 🔒🦀
tools
Use when the user wants to add a record into a DingTalk table through an automation webhook, especially when they describe the record in natural language, provide a Markdown file path as the content source, or need field validation, a field-summary preview, and explicit confirmation before sending. Image recognition is opt-in — only enabled when the user explicitly requests it.
development
Use when reviewing novel chapters or manuscripts for logic consistency, character authenticity, plot cohesion, foreshadowing payoff, emotional resonance, narrative vividness, and content compliance. Also triggers for first-chapter editorial audits against web novel platform submission standards. Triggers on requests like "check the story", "review this chapter", "is this consistent with character", "improve story flow", "add foreshadowing", "check content safety", "前三章审核", "过稿检查", "开篇钩子", "审查前三章", or "editorial submission check".
tools
UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn/ui MCP for component search and examples.
development
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.