Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Skill Dependency Fixer
v2.0.9Scan installed OpenClaw skills for missing npm, pip, brew, or system dependencies and auto-install fixable ones.
⭐ 1· 92·0 current·0 all-time
byChristian Teo@christianteohx
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's high-level purpose matches the instructions: scanning ~/.openclaw for SKILL.md and detecting npm/pip/brew/bin issues is coherent. However, the SKILL.md frontmatter claims it requires the 'node' binary (metadata.openclaw.requires.bins: ["node"]) while the registry metadata you provided lists no required binaries — that mismatch should be resolved.
Instruction Scope
The SKILL.md tells the agent to 'generate a complete Node.js CLI project' and to scan and then optionally auto-fix dependencies by invoking system package managers (brew, npm -g, pip). 'Generate a project' is vague and implies writing files to disk; auto-fixing implies running system-wide installers that may require elevated privileges. It also instructs use of clawhub inspect/update which fetches and modifies other skills' SKILL.md. The instructions therefore go beyond read-only scanning into creating code and performing system-level package operations — this is a scope expansion that should be explicit and gated.
Install Mechanism
There is no install spec (instruction-only), but the document recommends installing the tool from a third-party Homebrew tap and via curl from GitHub releases. These recommended install mechanisms (third-party tap, direct curl-to-binary) are higher-risk and should be treated with caution. Because the skill will tell the agent how to install and run code it generates or downloads, there's potential to execute arbitrary code if the sources are untrusted.
Credentials
The skill declares no required environment variables or credentials (registry metadata), which is appropriate for its stated purpose. However, the SKILL.md's metadata claims node is required but that wasn't declared in the registry metadata — a minor proportionality mismatch. The instructions do not request secrets, which is good.
Persistence & Privilege
always:false (no permanent forced presence). The skill allows autonomous invocation (default), so an agent could run the --fix flow and perform system installs without explicit additional confirmation unless the platform prevents that. Combining autonomous invocation with system package operations increases blast radius; prefer requiring explicit user confirmation for fixes and running dry-run by default.
What to consider before installing
This skill's goal is reasonable, but treat it as suspicious until you verify the implementation: 1) Confirm the GitHub repository and author (SKILL.md references a GitHub repo and a Homebrew tap 'christianteohx' — inspect them manually). 2) Prefer running the tool in --dry-run or review any generated Node.js project before executing or installing. 3) Do not run curl|sh or install binaries from unverified releases; prefer official package sources. 4) Be aware that --fix will invoke brew/npm/pip globally and may require privileges or change system state; run under a non-privileged account or in a disposable environment (VM/container) first. 5) Ask the maintainer to fix the metadata mismatch (node declared in SKILL.md but not in registry) and to make explicit whether the agent should auto-run installers or only produce an audit. If you want this skill to run automatically, require explicit confirmation before any system installs.Like a lobster shell, security has layers — review code before you run it.
dependenciesvk97bzke5te4v374zk4zrc33xgx84k23vlatestvk97ccsefyjy58h5dzrkd0gfg0x84k709openclawvk97ccsefyjy58h5dzrkd0gfg0x84k709skillsvk97ccsefyjy58h5dzrkd0gfg0x84k709
License
MIT-0
Free to use, modify, and redistribute. No attribution required.