BC insurance-claim-appeal
保险理赔纠纷维权辅助分析。当保险顾问的客户被保险公司拒赔时使用。逐条拆解拒赔理由、匹配保险法依据、规划维权路径，生成申诉函/投诉书/证据清单。 涵盖健康险（医疗险/重疾险）六大拒赔场景：未如实告知、等待期出险、既往症、免责条款、疾病定义争议、其他争议。 定位为保险专业咨询辅助工具，非法律执业服务。
保险理赔纠纷维权辅助分析。当保险顾问的客户被保险公司拒赔时使用。逐条拆解拒赔理由、匹配保险法依据、规划维权路径，生成申诉函/投诉书/证据清单。 涵盖健康险（医疗险/重疾险）六大拒赔场景：未如实告知、等待期出险、既往症、免责条款、疾病定义争议、其他争议。 定位为保险专业咨询辅助工具，非法律执业服务。
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 Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 150 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "triggers" - 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. 41 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 588 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
- +1No license
- +2Single-language instructions
- +3Description length 149: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 41 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.