SKILLEMALL.ai
GitHub ↗ RU Sign in

BC spot

Binance Spot request using the Binance API. Authentication requires API key and secret key. Supports testnet, mainnet, and demo.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 5 files body ≈ 7 168 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Binance Spot request using the Binance API.

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

IntegrationAI and agentstype 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
86/100
safety, quality, tests
Safety 60%
99
Quality 40%
67
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 read-dotenv SKILL.md:308
    Reads a .env file (detector / deny-list definition)
    * Never source a secrets file into the shell environment (`source .env` or `. .env`)
    detector

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 7168 tokens (recommended < 5000); move details to references/
  • note edit-residue the text marks something as outdated (lines 32): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 54/100

  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 7 mutating operations with no state check
  • 40Consistency. Frontmatter name (spot) differs from the folder (binance-spot)
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Failures and branches. 10 branches
  • 70Execution cost. Instruction body is 7168 tokens
  • 100Steps. 183 steps
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 10 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
  • +2Single-language instructions
  • +3Description length 128: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 183 items
  • +4Has examples (4 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +1License stated

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