SKILLEMALL.ai
GitHub ↗ RU Sign in

BC fiat

Binance Fiat request using the Binance API. Authentication requires API key and secret key.

ClawHub Agent Skills author: Dexploarer v1.0.0 MIT-0 3 files body ≈ 1 735 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

IntegrationInfrastructuretype 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
89/100
safety, quality, tests
Safety 60%
99
Quality 40%
74
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.
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:127
    Reads a .env file (detector / deny-list definition)
    * Never source a secrets file into the shell environment (`source .env` or `. .env`)
    detector

Files scanned: 3. 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")

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. 4 mutating operations with no state check
  • 40Consistency. Frontmatter name (fiat) differs from the folder (binance-fiat)
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 60Failures and branches. 2 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 39 steps
  • 100Execution cost. Instruction body is 1735 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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)
  • +3Description length 91: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 39 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: 74.

External checks

ClawHub: suspicious
This Binance helper is related to its stated purpose, but it gives an agent too much unsupervised access to financial API credentials and stores them in a plaintext local file.
LLM: suspicious (high) · VirusTotal: · 29 May 2026