AC vertical-home-reno-estimator
装修造价估算工具（Vertical品牌）。 用户输入房屋面积、装修档次、所在城市，AI生成专业的装修造价估算报告。 触发场景： - 用户问"装修要花多少钱"、"帮我估算装修成本" - 用户提到"住宅装修"、"家装预算"、"装修报价" - 用户需要快速估算装修费用区间 输出：结构化估算报告（总价区间 + 分项拆解 + 不确定项提示 + 数据来源说明）
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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: 41. 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 53/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
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 796 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -33 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 177: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (2 of 14)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.
External checks
ClawHub: suspicious
The core estimator appears local and non-destructive, but the package also ships under-disclosed marketing, payment, sharing, and unrelated business-guidance material.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026