SKILLEMALL.ai

AC data-viz-wizard

Transform CSV data into stunning interactive chart visualizations with Chart.js

ClawHub Hermes author: voronindenis5 v0.1.0 MIT-0 9 files body ≈ 569 tokens Open the sourceclawhub.ai analyzed 2 d ago

Transform CSV data into stunning interactive chart visualizations with Chart.js

As a process C 60/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

GeneratorData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
74
Run on models
none yet
Process rating
C
60/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
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. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 79 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill

Process rating: all ten parameters 60/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 85Steps. 12 steps, 1 vague phrases
  • 100Tools and files. No external tools needed
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 569 tokens
  • 100Running it twice. No mutating operations
  • low The response is described with custom markup (3 tags): a typed call is more reliable

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 79: 120–800 characters recommended
  • +2Single-language instructions
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 12 items
  • +3Output format is stated explicitly
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)
  • +3All 1 scripts are documented
  • +1License stated

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

External checks

ClawHub: suspicious
This CSV chart skill is useful, but its generated reports run browser JavaScript, load Chart.js from a third-party CDN, and do not safely escape some CSV-derived text.
LLM: suspicious (high) · 14 Aug 2026