Tencent SkillHub · Security & Compliance

Skill Vettr

Static analysis security scanner for third-party OpenClaw skills. Detects eval/spawn risks, malicious dependencies, typosquatting, and prompt injection patte...

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

Static analysis security scanner for third-party OpenClaw skills. Detects eval/spawn risks, malicious dependencies, typosquatting, and prompt injection patte...

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: .gitignore, package-lock.json, package.json, readme.md, skill.md, tsconfig.json

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 2.0.3

Provenance

Publisher: britrik
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 10 sections Open source page

skill-vettr v2.0.3

Security scanner for third-party OpenClaw skills. Analyses source code, dependencies, and metadata before installation using tree-sitter AST parsing and regex pattern matching.

Installation

npm install This installs all Node.js dependencies, including tree-sitter .wasm grammar files required at runtime for AST-based analysis. The .wasm files are located in node_modules and must be present for the skill to function. ⚠️ Install safety: npm install runs dependency lifecycle scripts, which can execute arbitrary code. For stronger isolation, run npm ci --ignore-scripts — but note that tree-sitter native/WASM artifacts may not build, breaking AST analysis. Prefer installing inside a container or VM when possible.

External Binaries

The vet-url and vet-clawhub commands invoke external binaries via execSafe (which uses execFile — no shell is spawned). Only the following commands are permitted: BinaryUsed ByPurposegitvet-urlClone .git URLs (with hooks disabled)curlvet-urlDownload archive URLstarvet-urlExtract downloaded archivesclawhubvet-clawhubFetch skills from ClawHub registry The /skill:vet command (local path vetting) requires only node and no external binaries.

Commands

/skill:vet --path <directory> — Vet a local skill directory /skill:vet-url --url <https://...> — Download and vet from URL /skill:vet-clawhub --skill <slug> — Fetch and vet from ClawHub

Detection Categories

CategoryMethodExamplesCode executionASTeval(), new Function(), vm.runInThisContext()Shell injectionASTexec(), execSync(), spawn("bash"), child_process importsDynamic requireASTrequire(variable), require(templateString)Prototype pollutionASTproto assignmentPrompt injectionRegexInstruction override patterns, control tokens (in string literals)Homoglyph attacksRegexCyrillic/Greek lookalike characters in identifiersEncoded namesRegexUnicode/hex-escaped "eval", "exec"Credential pathsRegexCloud and SSH credential directory references, system credential store accessNetwork callsASTfetch() with literal URLs (checked against allowlist)Malicious depsConfigKnown bad packages, lifecycle scripts, git/http depsTyposquattingLevenshteinSkill names within edit distance 2 of targetsDangerous permissionsConfigshell:exec, credentials:read in SKILL.md

Limitations

⚠️ This is a heuristic scanner with inherent limitations. It cannot guarantee safety. Static analysis only — Cannot detect runtime behaviour (e.g., code that fetches malware after install) Evasion possible — Sophisticated obfuscation or multi-stage string construction can evade detection JS/TS only — Binary payloads, images, and non-text files are skipped Limited network detection — Only detects fetch() with literal URL strings; misses axios, http module, dynamic URLs No sandboxing — Does not execute or isolate target code Comment scanning — Prompt injection detection scans string literals, not comments Filesystem scope — vet-url downloads and extracts remote archives into a temp directory; vet accepts paths under os.tmpdir(), ~/.openclaw, and ~/Downloads by default. Set allowCwd: true in config to also permit process.cwd() (see Configuration below) External binary trust — vet-url and vet-clawhub invoke git, curl, tar, and clawhub via execFile. These binaries must be trusted and present on PATH For high-security environments, combine with sandboxing, network isolation, and manual source review. Run inside a disposable container when vetting untrusted URLs.

allowCwd

By default, process.cwd() is not included in the set of allowed vetting roots. The default allowed roots are: os.tmpdir() ~/.openclaw ~/Downloads To allow vetting paths under the current working directory, set allowCwd: true in your vetting config: { "allowCwd": true } ⚠️ Security implication: Enabling allowCwd means the scanner will accept any path under the directory you launched it from. If you run from / or $HOME, this effectively grants access to your entire filesystem. Only enable this when running from a scoped project directory or inside a container.

.vettrignore

Place a .vettrignore file in the root of the skill directory being scanned to exclude files or directories from analysis. This is useful for excluding test fixtures that contain deliberate malicious patterns.

Format

One glob pattern per line Lines starting with # are comments Empty lines are ignored Patterns ending with / match entire directories * matches any sequence of non-separator characters ** matches any sequence including path separators (recursive) ? matches a single non-separator character

Example

# Exclude test fixtures containing deliberate prompt injection vectors test/fixtures/ # Exclude generated files dist/ *.min.js If the .vettrignore file is unreadable or contains invalid UTF-8, the engine logs an INFO-level warning and proceeds with a full scan.

Category context

Identity, auth, scanning, governance, audit, and operational guardrails.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

3 Config2 Docs1 Files

readme.md Docs
skill.md Docs
package-lock.json Config
package.json Config
tsconfig.json Config
.gitignore Files