SKILLEMALL.ai

AC crypto-levels

Analyze cryptocurrency support and resistance levels. Use when users ask about crypto price analysis, support/resistance levels, technical analysis for BTC, ETH, or other cryptocurrencies. Provides current price, key levels, and trading insights for crypto pairs like BTC-USDT, ETH-USDT.

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

Analyze cryptocurrency support and resistance levels.

As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerResearchtype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
99
Quality 40%
85
Run on models
none yet
Process rating
C
56/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

    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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Exfiltration exfil-webhook-url references/CONFIGURATION.md:569
      Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
      "slack": "https://hooks.slack.com/...",
      placeholder

    Files scanned: 16. 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 56/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
    • 20When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 85Steps. 97 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1945 tokens
    • 100Running it twice. No mutating operations
    • 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

    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)
    • +3Output format is not stated: the model decides each time
    • -36 of 6 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 287: enough signal without eating the budget
    • +4Structure: 44 headings
    • +3Step-by-step instructions: 97 items
    • +4Has examples (6 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)

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