BC property-dispute
[Property] 物业纠纷全流程维权助手。业主描述物业问题（电梯故障/漏水/物业费涨价/账目不透明/公共收益被侵占/服务不达标等），自动完成权利评估-法律条款速查-升级流程导航-投诉文件生成-谈判脚本输出-公共税务审计6大阶段分析，生成交互式HTML可视化维权报告。覆盖民法典物权编/物业服务合同/侵权责任、物业管理条例、消防法、税收征管法等法律法规，提供住建局/市场监管局/税务局/消防等多部门联合举报策略。触发词：物业纠纷, 物业问题, 电梯坏了, 漏水, 物业费涨价, 物业费涨了, 物业不管, 物业维权, 投诉物业, 业主维权, 物业投诉, 物业不作为, 天花板漏水, 公共收益, 物业查账, property dispute, 物业起诉, 退物业费, 解聘物业, 物业财务, 物业账目。
[Property]…
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.
- 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: 6. 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") - note
frontmatter-keyunknown frontmatter key "agent_created"
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. 91 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 816 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 350: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 91 items
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.