BF Claims Expert Digital Employee
覆盖理赔报案受理、材料处理、医疗审核、责任认定、理算调度、欺诈检测、核赔决策、结案通知全链路。从报案到结案的一站式智能理赔处理能力。
覆盖理赔报案受理、材料处理、医疗审核、责任认定、理算调度、欺诈检测、核赔决策、结案通知全链路。从报案到结案的一站式智能理赔处理能力。
As a process F 24/100 · Will not run — References files that are not bundled: 机构既有规范或功能
ProcedureInfrastructureAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 11414 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: 机构既有规范或功能 - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "capabilities"
Process rating: all ten parameters 24/100
Will not run. References files that are not bundled: 机构既有规范或功能
- 0Tools and files. 1 referenced file(s) missing: 机构既有规范或功能
- 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
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (Claims Expert Digital Employee) differs from the folder (claim-expert-digital-employee)
- 40Execution cost. Instruction body is 11414 tokens: crowds the task out of the window
- 100Steps. 524 steps
- low 115 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 66: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -212 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 219 headings
- +3Step-by-step instructions: 524 items
- +4Has examples (20 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 44.
External checks
ClawHub: suspicious
This is a claims-workflow reference skill, but it contains contradictory instructions about local logs, long retention, and high-impact claims actions.
LLM: suspicious (high) · 10 Sept 2026