SKILLEMALL.ai

CB tokenomics-decoder

(no description)

ClawHub Hermes author: heroinyan-stack v1.0.0 MIT-0 2 files body ≈ 3 748 tokens Open the sourceclawhub.ai analyzed 33 h ago

This Skill: paste a contract address → 30 seconds later you get a full tokenomics report with unlock pressure score + rug pull risk matrix + comparison vs 50…

As a process B 68/100 · Nearly there — weak spots: when it triggers, running it twice, progress reporting

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
74/100
safety, quality, tests
Safety 60%
100
Quality 40%
34
Run on models
none yet
Process rating
B
68/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
30
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • error description-missing SKILL.md: no `description` — the skill can never trigger
  • note frontmatter-key unknown frontmatter key "sub_category"
  • note frontmatter-key unknown frontmatter key "trigger_keywords"
  • note frontmatter-key unknown frontmatter key "pricing"

Process rating: all ten parameters 68/100

  • 0Progress reporting. Says nothing while it works
  • 30When it triggers. No condition that starts the skill
  • 30Running it twice. 10 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 36 steps, 1 vague phrases
  • 100Failures and branches. 3 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3748 tokens
  • 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 0: 120–800 characters recommended
  • -263 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 36 items
  • +3Output format is stated explicitly
  • +4Has examples (5 code blocks)

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

External checks

ClawHub: suspicious
The skill is mostly a disclosed crypto due-diligence report generator, but it contradicts its own educational-only limits by requiring direct hold/dump/daytrade-style guidance.
LLM: suspicious (high) · 13 Aug 2026