Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Skill Vetter.Bak
v1.0.0Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope,...
⭐ 0· 60·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (skill vetter) align with the SKILL.md: it only describes manual/automated checks and GitHub queries. However the SKILL.md uses curl and jq examples but the skill metadata declares no required binaries — a mismatch that could cause runtime failures or unexpected behavior.
Instruction Scope
Instructions focus on reviewing skill files and checking repository metadata. They do not instruct the agent to access unrelated system credentials or config files. They do include 'Read ALL files in the skill' (which is appropriate) and example commands that perform network calls to GitHub/raw.githubusercontent; the agent will need network access to run those examples.
Install Mechanism
Instruction-only skill with no install spec and no code files — low disk-write risk. There is no download/install behavior declared in the skill itself.
Credentials
The skill requests no environment variables or credentials, which is appropriate. It does assume availability of networking and CLI tools (curl, jq) but does not declare them. No sensitive secrets are requested.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent presence or elevated privileges. Nothing in SKILL.md instructs it to modify other skills or system-wide configs.
What to consider before installing
This skill is fundamentally coherent: it describes how to vet other skills and gives concrete checks and example commands. Before installing/using it, verify two small issues: (1) the SKILL.md examples use curl and jq but the registry metadata doesn't list required binaries — ensure your agent environment actually has those tools or update the skill to declare them; (2) the _meta.json ownerId/publishedAt differ from the registry metadata shown — confirm the skill author and source to avoid supply-chain confusion. Also remember the vetter will perform network calls (GitHub/raw.githubusercontent) when run — treat network access and fetched content as untrusted and do a manual review for high-risk skills.Like a lobster shell, security has layers — review code before you run it.
latestvk977d2h543e3ng8859qnky6jb583qb1k
License
MIT-0
Free to use, modify, and redistribute. No attribution required.