BD smyx-cutting-rooting-status-detection-analysis
AI-powered non-invasive rooting-stage detection for plant cuttings in transparent containers. From smart propagation boxes or transparent cutting containers, periodically captures images of the cutting base (water roots or substrate roots visible through the transparent wall), uses AI vision to detect white root primordia (tiny white callus dots) and count/locate them, and outputs the rooting stage (No Roots / Few Primordia / Many Primordia / Well-Developed Roots). Helps propagators monitor cutting-rooting progress without disturbing the cutting and choose the optimal transplant time. Scenarios: smart propagation boxes, home cutting propagation, tissue-culture rooms, agricultural research. | 通过智能育苗箱或透明扦插容器的固定摄像头，定期拍摄枝条基部的水生根或土培根系（通过透明壁观察），利用AI视觉分析技术识别枝条基部是否出现白色凸起根点（根原基发育形成的白色小点）以及根点的数量和分布，输出生根阶段（无生根/少量根点/大量根点/根系发达）。该技能帮助育苗者在不干扰枝条的情况下，无创监测扦插生根进度，判断移栽时机。应用场景：智能育苗箱、家庭扦插繁殖、植物组培室、农业科研。
As a process D 35/100 · Unfinished process — weak spots: steps, result and completion, when it triggers
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 30. 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 35/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
- 25Steps. 1 steps
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1472 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 893: 120–800 characters recommended
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- -256 emoji in the instructions: noise for the model
- -32 of 4 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Structure: 19 headings
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.