SKILLEMALL.ai

BF plant-wilting-monitoring-analysis

Early monitoring of plant wilting based on hyperspectral imaging and computer vision, captures early wilting signs before visible symptoms, provides early warning for precision irrigation and disease control. | 植物枯萎监测技能,基于高光谱成像与计算机视觉,在肉眼可见症状前捕捉早期枯萎迹象,为精准灌溉和病害防控提供早期预警

ClawHub Agent Skills v1.0.13 29 files body ≈ 1 402 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process F 19/100 · Will not run — References files that are not bundled: references/api_doc.md

AnalyzerInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
59
Run on models
none yet
Process rating
F
19/100
Will not run
References files that are not bundled: references/api_doc.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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. The text references files that are not there: add them or drop the references.
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: 29. 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")
  • warning missing-ref reference to a missing file: references/api_doc.md

Process rating: all ten parameters 19/100

Will not run. References files that are not bundled: references/api_doc.md
  • 0Tools and files. 1 referenced file(s) missing: references/api_doc.md
  • 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
  • 25Steps. 1 steps
  • 40Consistency. Frontmatter name (plant-wilting-monitoring-analysis) differs from the folder (smyx-plant-wilting-monitoring-analysis)
  • 100Execution cost. Instruction body is 1402 tokens
  • 100Running it twice. No mutating operations
  • low 10 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • -255 emoji in the instructions: noise for the model
  • -32 of 4 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +3Description length 267: enough signal without eating the budget
  • +4Structure: 20 headings
  • +4Has examples (3 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This skill offers plant media analysis, but it needs review because it can send media, identity data, and authentication tokens over insecure HTTP and stores tokens locally.
LLM: suspicious (high)