BF Insurance Claims Intelligence Expert
Advisory skill for insurance claims processing workflows — provides templates, checklists, and decision-support frameworks for medical OCR, liability determination, anti-fraud assessment, and claims reporting. Human review required for all claim decisions. Keywords: insurance claims, claims advisory, medical OCR, anti-fraud, insurance tech, China insurance, decision support, 智能理赔, 理赔风控, 医疗单据识别, 责任认定, 理赔报告, 秒赔, 理赔决策, 医疗险理赔, 重疾理赔, 车险理赔.
As a process F 36/100 · Will not run — References files that are not bundled: references/claims_ocr_tech.md, references/claims_liability_engine.md, references/claims_report_templates.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Advisory skill for insurance claims processing workflows — provide… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - 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
missing-refreference to a missing file: references/claims_ocr_tech.md - warning
missing-refreference to a missing file: references/claims_liability_engine.md - warning
missing-refreference to a missing file: references/claims_report_templates.md - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "capabilities"
Process rating: all ten parameters 36/100
- 0Tools and files. 3 referenced file(s) missing: references/claims_ocr_tech.md, references/claims_liability_engine.md, references/claims_report_templates.md
- 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. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (Insurance Claims Intelligence Expert) differs from the folder (insurance-claims-intelligence)
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 7 steps
- 100Execution cost. Instruction body is 2135 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- -214 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 438: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 7 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 44.