SKILLEMALL.ai
GitHub ↗ RU Sign in

AD clash-node-manager

Manages Clash proxy nodes. Allows listing current node with connection status, listing available nodes, and switching to a specified node. Use when the user asks to manage Clash proxy settings, view available nodes, or switch between them.

modbender/skill-library-mcp Agent Skills author: modbender MIT 3 files body ≈ 348 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Manages Clash proxy nodes.

As a process D 41/100 · Unfinished process — weak spots: steps, result and completion, inputs and preconditions

ReferenceSoftware developmenttype 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
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
77
Run on models
none yet
Process rating
D
41/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    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: 3. 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 41/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 25Steps. 1 steps
    • 60Tools and files. Uses tools (python, node) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 348 tokens
    • 100Running it twice. No mutating operations
    • low The response is described with custom markup (6 tags): a typed call is more reliable

    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
    • +4Description does not say when NOT to use the skill (false activations)
    • +3No numbered steps or checklist
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 239: enough signal without eating the budget
    • +4Structure: 8 headings

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