BC geoskill-orchard-tree-counting
基于 CHM 峰值检测与模板匹配统计果树株数与冠幅。Counts orchard trees and crown widths from CHM peak detection and template matching.
基于 CHM 峰值检测与模板匹配统计果树株数与冠幅。Counts orchard trees and crown widths from CHM peak detection and template matching.
As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 20. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 62/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
- 100Tools and files. No external tools needed
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 501 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 110: 120–800 characters recommended
- +2Single-language instructions
- +4Structure: 20 headings
- +3Step-by-step instructions: 4 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.
External checks
ClawHub: suspicious
The main tree-counting command is local, but the package also ships under-disclosed network, credential-reading, cache, and hardcoded credential code that does not fit the stated offline orchard-counting purpose.
LLM: suspicious (high) · 4 Aug 2026