guidewire-core-workflow-b
Execute Guidewire secondary workflow: Claims processing in ClaimCenter. Use when implementing FNOL, claim investigation, reserves, payments, and settlement. Trigger with phrases like "claimcenter workflow", "create claim", "file fnol", "process claim", "claim settlement", "claim payment".
- License 许可
- MIT
- 最近更新
- 2026-05-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- guidewire-core-workflow-b
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Execute Guidewire secondary workflow: Claims processing in ClaimCenter. Use when implementing FNOL, claim investigation, reserves, payments, and settlement. Trigger with phrases like "claimcenter workflow", "create claim", "file fnol", "process claim", "claim settlement", "claim payment".
- allowed-tools
- Read, Write, Edit, Bash(curl:*), Bash(npm:*), Grep
- compatible-with
- claude-code, codex, openclaw
02 资源文件 1
- 参考文档references/implementation-guide.md10.4 KB
03 SKILL.md 正文
Guidewire Core Workflow B: Claims Processing
Overview
Master the complete claims lifecycle in ClaimCenter: First Notice of Loss (FNOL), claim investigation, reserve setting, payments, and settlement.
Prerequisites
- Completed
guidewire-install-authandguidewire-core-workflow-a - Understanding of claims handling processes
- Valid API credentials with claims admin permissions
Claims Lifecycle States
FNOL -> Open -> Investigation -> Evaluation -> Negotiation -> Settlement -> Closed
[Draft] [Open] [Reserve] [Exposure] [Payment] [Settle] [Closed]
Instructions
Step 1: Create FNOL
POST to /fnol/v1/fnol with loss date, loss type/cause, description, policy number, loss location, and reporter details.
Step 2: Add Exposures
POST exposures to /claim/v1/claims/<claimId>/exposures specifying exposure type (VehicleDamage, BodilyInjury), loss party (insured, claimant), and primary coverage.
Step 3: Add Incidents
POST vehicle incidents with severity, damage description, vehicle details, and operability status.
Step 4: Set Reserves
POST reserves to each exposure specifying reserve line (indemnity, expenses), cost type, category, and amount.
Step 5: Create Payments
POST payments with payment type (partial, final), exposure reference, payee, reserve line, amount, and payment method (check).
Step 6: Close Exposures
POST to each exposure's /close endpoint with the closed outcome (completed, denied, duplicate).
Step 7: Close Claim
POST to /claim/v1/claims/<claimId>/close with outcome. All exposures must be closed first.
For complete TypeScript API calls and Gosu server-side implementations, load the reference guide:
Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
Output
- FNOL claim with claim number
- Exposures linked to coverages
- Reserves set on exposures
- Payments processed
- Claim closed with outcome
Error Handling
| Error | Cause | Solution |
|---|---|---|
Policy not found |
Invalid policy number | Verify policy number and status |
Coverage not applicable |
Wrong coverage type | Check policy coverages |
Reserve exceeds limit |
Over policy limit | Adjust to policy limits |
Payment validation |
Missing required fields | Check payee and amount |
Cannot close |
Open activities/exposures | Complete pending items |
Resources
Next Steps
For error handling patterns, see guidewire-common-errors.
Examples
Auto collision claim: File an FNOL for a two-vehicle accident, create VehicleDamage and BodilyInjury exposures, set reserves of $5,000 for vehicle repair and $2,000 for medical expenses, issue a partial payment to the body shop, then close exposures and the claim after settlement.
Property damage claim with subrogation: File an FNOL for water damage at a commercial property, create a PropertyDamage exposure, set indemnity reserves, process payments to the restoration contractor, pursue subrogation against the responsible party, and close the claim with recovered amounts.
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
zustand-store-creator
Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.
zero-trust-config-helper
Zero Trust Config Helper - Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category.
zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
zai-cli
Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP. Use when user needs image/video analysis, OCR, UI-to-code conversion, error diagnosis, real-time web search, web page to markdown extraction, or GitHub code exploration. Trigger with phrases like "analyze this image", "search the web for", "read this page", "explore this repo", or "use zai". Requires Z_AI_API_KEY.
yt-research
Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.