SKILLEMALL.ai

AB crunch-coordinate

Use when managing Crunch coordinators, competitions (crunches), rewards, checkpoints, staking, or cruncher accounts via the crunch-cli.

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

Translates natural language queries into crunch-cli commands.

As a process B 70/100 · Nearly there — weak spots: when it triggers, progress reporting

IntegrationSlackTelegramDiscordAI and agentsWriting and documentsSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
98
Quality 40%
91
Run on models
none yet
Process rating
B
70/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Tools and files w 18
60
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 · 2

    ✓ No critical or high findings

    Medium and low: 2
    • low Secrets in code secret-high-entropy-token references/cli-reference.md:70
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      crunch-cli coordinator get "9WzD…WWM"
      quoted
    • low Secrets in code secret-high-entropy-token references/cli-reference.md:118
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      crunch-cli crunch list "9WzD…WWM"
      quoted

    Files scanned: 2. 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 70/100

    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (node) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 27 steps, 1 vague phrases
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1435 tokens
    • 100Running it twice. Mutating operations check current state
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 11 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (28 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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 135: enough signal without eating the budget
    • +4Structure: 14 headings
    • +3Step-by-step instructions: 27 items
    • +3Output format is stated explicitly
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)

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