claims-triage
Triage an incoming insurance claim: check the coverage trigger against policy wording, band severity and complexity, screen for fraud indicators, set a first-pass reserve range, and route with an SLA
Install / Use
npx skills add mohitagw15856/pm-claude-skills --skill claims-triageInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of claims-triage
claims-triage scores 82/100 on our quality scale, 2918th of 4,658 Development & Engineering skills we index.
Its SKILL.md is 5.6 KB long, well organised into 8 sections and no code examples: a solid amount of guidance for an agent.
With 1,396 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 8 days ago, so claims-triage is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
claims-triage compared with similar skills
All 4 of these similar skills score higher than claims-triage; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| claims-triage (this skill)by mohitagw15856 | 82 | 1.4k | 8d ago | SKILL.md |
| ai-job-searchby MadsLorentzen | 100 | 44.8k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 41.7k | 2d ago | CLAUDE.md |
| algorithmic-artby anthropics | 100 | 177.9k | 10d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 10d ago | SKILL.md |
Frequently asked questions
- How do I install claims-triage?
- Run
npx skills add mohitagw15856/pm-claude-skills --skill claims-triage. The install tabs above show the steps for each supported agent. - Which AI agents does claims-triage work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is claims-triage safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is claims-triage still maintained?
- The repository was last updated 8 days ago, so claims-triage is actively maintained.
Skill content
View source on GitHubname: claims-triage description: "Triage an incoming insurance claim: check the coverage trigger against policy wording, band severity and complexity, screen for fraud indicators, set a first-pass reserve range, and route with an SLA. Use when asked to triage a claim, review a first notice of loss (FNOL), assess a new claim, decide fast-track vs adjuster routing, or screen a claim for SIU referral. Produces a structured triage note with coverage view, severity band, indicator screen, reserve range, and a routing recommendation."
Claims Triage Skill
The first 24 hours of a claim set its cost and its customer experience. This skill runs a disciplined first-pass triage: does the policy respond, how big and how complicated is this, are there indicators that warrant investigation, what should we hold in reserve, and who should own it by when.
What This Skill Produces
- A coverage-trigger view against the actual policy wording (trigger, exclusions, conditions)
- A severity/complexity band with rationale
- A fraud-indicator screen — indicators only, never conclusions
- A first-pass reserve range (indemnity + expense), labelled as first-pass
- A routing recommendation (fast-track / adjuster / senior adjuster / SIU referral / coverage counsel) with SLA
Required Inputs
Ask for these if not provided; if working from a thin FNOL, proceed and label every inference [assumed — confirm]:
- Loss description — what happened, when, where, reported when
- Policy details — line of business, wording or key clauses, limits, deductible, period
- Claimed amount or damage description (even rough)
- Claimant/insured history if available (prior claims, tenure)
Triage Framework
1. Coverage trigger. Quote or paraphrase the operative insuring clause. State: trigger met / trigger uncertain / trigger likely not met — with the specific wording reason. Sweep exclusions and conditions precedent (notification timing, security warranties). If coverage is uncertain, flag a reservation-of-rights consideration and route to coverage counsel review — never let uncertainty default to "covered".
2. Severity/complexity banding:
| Band | Profile | Typical routing | |---|---|---| | 1 — Fast-track | Clear coverage, quantum near/below deductible-adjacent threshold, no injury, single party | Automated/desk settlement | | 2 — Standard | Clear coverage, moderate quantum, routine investigation | Adjuster | | 3 — Complex | Large loss, bodily injury, multiple parties, coverage questions, or business interruption | Senior adjuster, early expert instruction | | 4 — Major/CAT | Catastrophe-linked, potential limit loss, litigation likely, reputational exposure | Major-loss team + counsel, executive notification |
Band on the worse of severity and complexity.
3. Fraud-indicator screen. Check common indicators: loss shortly after inception or cover increase, late reporting without explanation, documentation inconsistencies, over-documentation, prior similar claims, financial-distress signals, uncooperative or steering behaviour, loss narrative inconsistent with physical evidence. State only which indicators are present and absent. Two or more material indicators → recommend SIU referral in parallel with normal handling; the claim is still handled in good faith.
4. First-pass reserve. Give a range for ultimate incurred: indemnity + expense (adjusting, legal, experts), gross and net of deductible. State the basis (repair estimate, comparable claims, injury tariff) and label it first-pass, to be revised on investigation.
5. Routing + SLA. Name the route, the required first contact/action, and the SLA (e.g. fast-track: decision in 5 business days; Band 3: insured contacted within 24h, site inspection within 5 days).
Output Format
Claim triage: [claim ref / insured / loss date]
1. Loss summary — 2–3 sentences, facts only. 2. Coverage trigger — clause cited, trigger view, exclusions/conditions checked, open coverage questions. 3. Severity band — band + one-line rationale. 4. Indicator screen — table: indicator | present? | evidence. Then: SIU referral recommended yes/no. 5. First-pass reserve — range, basis, gross/net. 6. Routing & SLA — route, owner type, first actions with deadlines. 7. Information needed — the specific documents/statements to request next.
End every triage note with: "This is analytical support for triage, not a coverage determination. Coverage, reserving, and referral decisions follow your organisation's claims-handling policy and applicable regulation."
Quality Checks
- [ ] Coverage view cites specific wording, not just line of business
- [ ] Severity band has a stated rationale and used the worse of severity/complexity
- [ ] Fraud screen lists indicators present and checked-but-absent — no conclusion stated
- [ ] Reserve is a range with a stated basis, labelled first-pass, gross and net shown
- [ ] Routing includes an SLA and concrete first actions
- [ ] Assumptions from a thin FNOL are labelled
[assumed — confirm] - [ ] Regulatory support-not-determination line is included
Anti-Patterns
- [ ] Do not state a fraud conclusion — state indicators and route to SIU; the word is "indicator", never "fraudulent"
- [ ] Do not let a SIU referral pause good-faith handling of the claim
- [ ] Do not default an uncertain trigger to "covered" or "denied" — flag it for coverage review with the wording question stated
- [ ] Do not give a single-point reserve on day one — give a range with basis
- [ ] Do not invent policy terms — if the wording isn't provided, ask, or label the clause
[to confirm against wording]
Related Skills
ai-job-search
44.8kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
41.7kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
