BB mobula-prices
Real-time token prices, market caps, volume, and analytics across 88+ blockchains. Free tier, no credit card required.
As a process B 74/100 · Nearly there — weak spots: inputs and preconditions, progress reporting
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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
-
medium Dangerous commands
cmd-shell-rcREADME.md:63Writes to a shell startup fileecho 'export MOBULA_API_KEY="your_key"' >> ~/.zshrc
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 118 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "requiredEnvVars" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "docs" - note
frontmatter-keyunknown frontmatter key "repository"
Process rating: all ten parameters 74/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 90 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1708 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 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
- +5Description has no quoted example phrases that should trigger the skill
- +3Description length 118: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 21 headings
- +3Step-by-step instructions: 90 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.