Skills/ClawHub/alibabacloud-lingjun-cluster-scaling

alibabacloud-lingjun-cluster-scaling@0.0.1-beta.3

CAUTION

Publisher claims: "Manage Alibaba Cloud Lingjun cluster scaling: extend clusters (add nodes), shrink clusters (remove nodes), create and update node groups, and move nodes between node groups (change node group). Run: every Bash call MUST begin with: export LJ_SKILL_DIR="the dir holding this skill" && export LJ_PLATFORM="qoder|text" && source "$LJ_SKILL_DIR/lib/lj_init.sh" (LJ_SKILL_DIR default: $HOME/.qoder/skills/alibabacloud-lingjun-cluster-scaling; LJ_PLATFORM: "qoder" in Qoder IDE, else "text") Triggers: "extend-cluster", "shrink-cluster", "create-node-group", "update-node-group", "change-node-group", "lingjun cluster", "灵骏集群", "灵骏扩容", "灵骏缩容", "lingjun node", "灵骏节点", "加节点", "减节点", "expand cluster", "shrink cluster", "node group", "节点组", "新建节点组", "创建节点组", "更新节点组", "迁移节点", "换组", "change group", "update node group", "scale out", "scale in", "add nodes", "remove nodes"" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher sdk-team · joined 12 days agoInstalls 209Last detonated 5d ago

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-10-29 and scored it 67/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Authorization escalation language. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

HIGH
Authorization escalation languagereferences/cli-installation-guide.md:95 · Authorization escalation languageFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01

No other findings across 5,026 lines in 16 files.

What would make this Verified

13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim sdk-team: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim sdk-team