SKILLEMALL.ai
RU Sign in

BC Dep Upgrade

Dependency audit and upgrade planner for Node.js, Python, Rust, Go, and Ruby projects. Scans for outdated packages, vulnerability CVEs, and breaking changes, then produces a prioritized upgrade plan with exact commands. Zero external API required — works entirely from your project files and standard package manager CLIs. Triggers on "audit dependencies", "check for vulnerabilities", "upgrade packages", "outdated deps", "/dep-upgrade".

ClawHub Agent Skills author: Lucius Pang v1.0.3 MIT-0 2 files body ≈ 1 899 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

AnalyzerSecuritySoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
C
55/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 55/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 40Consistency. Frontmatter name (Dep Upgrade) differs from the folder (phy-dep-upgrade)
  • 60Tools and files. Uses tools (python, node) that frontmatter does not declare
  • 70When it triggers. States when to use, but not when not to
  • 85Steps. 12 steps, 1 vague phrases
  • 100Failures and branches. 1 branches, has a failure section
  • 100Execution cost. Instruction body is 1899 tokens
  • 100Running it twice. Mutating operations check current state
  • low 10 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 5 example trigger phrases
  • +3Description length 438: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 12 items
  • +4Has examples (11 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.

External checks

ClawHub: suspicious
This dependency-audit skill appears useful, but it also tells agents to run package-changing fix commands under broad triggers without enough visible scoping or confirmation.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026