SKILLEMALL.ai

BD local-api-chart-generator

专为调用本地数据接口并生成图表展示定制的 Skill。接收自然语言指令(如“我要最近一年燃油类型为天然气的扭矩占比”),自动提取参数,请求本地接口,生成 HTML 柱状图并返回完整的 HTML 源码。

ClawHub Agent Skills author: z904832819 v1.0.3 MIT-0 4 files body ≈ 273 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
98
Quality 40%
65
Run on models
none yet
Process rating
D
46/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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.
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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Obfuscation obf-base64-blob build_chart.py:31
    Long base64-looking blob (quoted — discussed, not commanded)
    response = session.post(url_, json=params, timeout=10, headers={"Content-Type": "application/json","Authorization": "Bearer eyJh…VUZ
    quoted
  • low Obfuscation obf-base64-blob build_chart.py:42
    Long base64-looking blob (quoted — discussed, not commanded)
    response = session.post(url, json=params, timeout=10, headers={"Content-Type": "application/json","Authorization": "Bearer eyJh…UZF
    quoted

Files scanned: 4. 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 46/100

  • 0Result and completion. Does not say what the result is
  • 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
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 9 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 273 tokens
  • 100Running it twice. No mutating operations

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 100: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • +1No license
  • +2Single-language instructions
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 9 items
  • +4Has examples (3 code blocks)

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

External checks

ClawHub: suspicious
This skill has a clear charting purpose, but it hides important security-sensitive behavior including a bundled API token and unlabeled fallback data.
LLM: suspicious (high) · VirusTotal: · 29 May 2026