SKILLEMALL.ai
GitHub ↗ RU Sign in

BC cobo-tss-node

Manage a Cobo TSS Node for MPC threshold signing. Use when: setting up a new TSS Node, starting/stopping the node service, checking node status or health, signing for key share checkups, exporting shares for disaster recovery, backing up or updating the node, installing as a systemd or launchd service. NOT for: Cobo WaaS API integration, on-chain transaction building, or wallet UI.

Not recommendedcritical or high security findings
modbender/skill-library-mcp Agent Skills author: modbender MIT 9 files · 8 scripts body ≈ 2 046 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Manage a Cobo TSS Node for MPC threshold signing.

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

IntegrationInfrastructureAI and agentsData and analyticstype 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
81/100
safety, quality, tests
Safety 60%
76
Quality 40%
89
Run on models
none yet
Process rating
C
55/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
50
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
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 · 3

  • high Dangerous commands cmd-persistence scripts/node-ctl.sh:72
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    start)   launchctl load "$PLIST_FILE" 2>/dev/null || launchctl kickstart "gui/$(id -u)/$MACOS_LABEL" ;;
Medium and low: 2
  • medium Dangerous commands cmd-persistence scripts/install-service.sh:121
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)
    echo "  launchctl load $PLIST_FILE"
    code literal
  • low Dangerous commands cmd-persistence scripts/node-ctl.sh:51
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition; string literal in code, not executed)
    PLIST_FILE="$HOME/Library/LaunchAgents/com.cobo.tss-node.plist"
    detectorcode literal

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

Against the Agent Skills spec

✓ No remarks against the Agent Skills spec

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
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (node) that frontmatter does not declare
  • 85Steps. 48 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2046 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress

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

  • +5Description has no quoted example phrases that should trigger the skill
  • +3Output format is not stated: the model decides each time
  • -214 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 384: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 48 items
  • +4Has examples (12 code blocks)
  • +3All 7 scripts are documented

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