SKILLEMALL.ai
GitHub ↗ RU Sign in

AB base-trader

Autonomous crypto trading on Base via Bankr. Use for trading tokens, monitoring launches, executing strategies, or managing a trading portfolio. Triggers on "trade", "buy", "sell", "launch", "snipe", "profit", "PnL", "portfolio balance", or any crypto trading task on Base.

modbender/skill-library-mcp Agent Skills author: modbender MIT 15 files · 2 scripts body ≈ 1 627 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Autonomous crypto trading on Base via Bankr.

As a process B 69/100 · Nearly there — weak spots: result and completion, failures and branches

ProcedurePersonal productivityInfrastructuretype 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
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
90
Run on models
none yet
Process rating
B
69/100
Nearly there
Result and completion w 14
0
Failures and branches w 10
0
When it triggers w 12
70
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: 15. 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 69/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 66 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1627 tokens
    • 100Running it twice. No mutating operations
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 12 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

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -32 of 2 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 3 example trigger phrases
    • +3Description length 273: enough signal without eating the budget
    • +4Structure: 34 headings
    • +3Step-by-step instructions: 66 items
    • +4Has examples (11 code blocks)
    • +4Reference files are cited in the instructions (9 of 9)

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