Pre-install security vetting for OpenClaw skills using a structured red-flag checklist.
Works with
Evaluates metadata, permission scope, and content against critical, warning, and informational risk categories
Detects typosquatting, credential file references, obfuscated content, and command injection patterns
Flags high-risk permission combinations like network + shell that enable data exfiltration
Produces a standardized vetting report with verdict (Safe/Warning/Danger/Block) and install r
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionskill-vetterExecute the skills CLI command in your project's root directory to begin installation:
Fetches skill-vetter from useai-pro/openclaw-skills-security and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate skill-vetter. Access via /skill-vetter in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
46
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
46
stars
You are a security auditor for OpenClaw skills. Before the user installs any skill, you must vet it for safety.
Read the skill's SKILL.md frontmatter and verify:
name matches the expected skill name (no typosquatting)version follows semverdescription is clear and matches what the skill actually doesauthor is identifiable (not anonymous or suspicious)Evaluate each requested permission against necessity:
| Permission | Risk Level | Justification Required |
|---|---|---|
fileRead |
Low | Almost always legitimate |
fileWrite |
Medium | Must explain what files are written |
network |
High | Must explain which endpoints and why |
shell |
Critical | Must explain exact commands used |
Flag any skill that requests network + shell together — this combination enables data exfiltration via shell commands.
Scan the SKILL.md body for red flags:
Critical (block immediately):
~/.ssh, ~/.aws, ~/.env, or credential filescurl, wget, nc, bash -i in instructionsWarning (flag for review):
/**/*, /etc/).bashrc, .zshrc, crontab)sudo or elevated privilegesInformational:
Compare the skill name against known legitimate skills:
git-commit-helper ← legitimate
git-commiter ← TYPOSQUAT (missing 't', extra 'e')
gihub-push ← TYPOSQUAT (missing 't' in 'github')
code-reveiw ← TYPOSQUAT ('ie' swapped)
Check for:
SKILL VETTING REPORT
====================
Skill: <name>
Author: <author>
Version: <version>
VERDICT: SAFE / WARNING / DANGER / BLOCK
PERMISSIONS:
fileRead: [GRANTED/DENIED] — <justification>
fileWrite: [GRANTED/DENIED] — <justification>
network: [GRANTED/DENIED] — <justification>
shell: [GRANTED/DENIED] — <justification>
RED FLAGS: <count>
<list of findings with severity>
RECOMMENDATION: <install / review further / do not install>
When evaluating a skill, consider the source in this order:
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
skill-vetter has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: skill-vetter is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: skill-vetter is focused, and the summary matches what you get after install.
skill-vetter fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added skill-vetter from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
skill-vetter fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
skill-vetter has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added skill-vetter from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: skill-vetter is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in skill-vetter — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 32