Triages fictional insurance claims and summarizes key intake details and priority.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "claim-intake" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/aibast-agents-library/main/solutions/claims-processing/manual/skills/aibast_claim-intake_01/SKILL.md 2. Save it as ~/.claude/skills/aibast_claim-intake_01/SKILL.md 3. Reload skills and tell me it's ready
Based on the claims intake data, identify which fictional claim needs specialized handling first and state which review area it should go to. Separate observed evidence, your judgment, and recommended next steps.
Returns the priority claim ID, the appropriate review queue, and clearly separates evidence, judgment, and next steps.
Summarize this set of fictional claims by loss type, amount, current status, and fraud-review score, and note which claims need human review.
Produces a structured summary listing key fields per claim and flags items that require human review.
Triage only the specified fictional claim record and do not substitute another record. Provide source-backed evidence and state whether it should be routed to investigation or another specialized handling queue.
Provides a triage decision strictly for the specified record, with source-backed evidence and a recommended handling path.
Claims operations staff can use it on newly submitted records to summarize loss, amount, status, and fraud-review score, then decide which cases should move forward first.
When a team needs to decide whether a fictional claim should go to investigation or another specialized queue, this skill can provide an evidence-based triage result and next-step guidance for the specified record.
The README describes a claims intake triage skill for a synthetic pilot. It summarizes fictional claims by loss type, amount, status, and fraud-review score. The procedure emphasizes using the exact requested record or report scope, grounding answers in a synthetic operating snapshot, and separating observed evidence from calculated output and next-step recommendations. It also requires clear disclaimers that the result is not professional advice and that no external action has occurred, with authorized human review needed before action.
Summarizes fictional claims by loss, amount, status, and fraud-review score.
Persona: Claims Operations Leader
Prompt: Which incoming claim needs specialized handling first, and where should it be reviewed?
Expected synthetic evidence: CLM-2025-7003, Investigation.
It is used for claims intake triage questions. In the synthetic pilot context, it summarizes fictional claims by loss, amount, status, and fraud-review score, and supports priority decisions.
No. The documentation explicitly states that the result does not mean any approval, communication, filing, account change, payment, order, transaction, or other external action has occurred.
The output is based on fictional or synthetic records and should separate observed evidence, calculated or heuristic output, and proposed next steps. The documentation also requires stating that the result is not legal, regulatory, insurance, lending, tax, investment, or financial advice.
Find each line’s bottleneck and recommend which station to address first.
Generates controlled implementation checklists for human review.
Get a synthetic health overview of a loyalty program without changing it.
Review SIU indicators in claims and return explainable evidence with human review guidance.
Analyze loyalty tier thresholds, perks, progress, and tradeoffs without changing status.
Identifies tax-loss-harvesting candidates and required review controls.
Run structured legal client intake and generate organized case summaries.
Checks claim-file readiness and compiles evidence for human review.
Triage support tickets by priority, ownership, and duplicate or known issue checks.
Preview and coordinate vendor procurement for insurance claims investigations and reviews.
Prepare reviewable retention and service-recovery options for churn-related customer cases.
Search claims documents, retrieve clauses, and answer questions with governed local LLM workflows.