Agent skill · software engineering · jeremylongshore
guidewire-core-workflow-b
Automate the ClaimCenter FNOL→investigation→reserve→payment→settlement→close pipeline including the failure paths — duplicate FNOL from multi-source intake, reserve-must-precede-payment ordering, supervisor-authorization tiers, premature settlement, and reopen-vs-new-claim ambiguity. Use when building claim intake from caller portals, IVR, or partner systems; automating reserve-setting jobs; or integrating settlement events with finance. Trigger with "claimcenter automation", "FNOL", "claim reserve", "claim payment", "claim settlement", "claim reopen".
Why this skill is useful
Adds executable scripts for automating the ClaimCenter claims lifecycle, including handling complex failure paths that aren't covered in public documentation.
What it needs
Requires bash installed locally. Requires guidewire account access. About 6k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Guidewire ClaimCenter Workflow Overview Drive the ClaimCenter claims lifecycle through Cloud API and survive the failure modes that derail naive automation. This is the workflow used by FNOL portals, IVR claims intake, partner-of-record APIs, and reserve-setting jobs. Assumes guidewire-install-auth provides the bearer token and guidewire-sdk-patterns provides the retrying client with checksum round-trip. Five production failures this skill prevents: 1. Duplicate FNOL from multi-source intake — the same loss event is reported by the caller, the claimant, and the broker; without dedup logic three claims land on the same loss with three reserves. 2. Payment before reserve — code creates a payment without first setting a reserve in the matching cost category; API returns 422 reserve-required. 3. Authorization-tier violation — an integration with payment role cc.payment.write attempts a payment above its authorization limit; API returns 422 authorization-required and the payment lands in pending-approval. 4. Premature settlement — claim closed before all open reserves are zeroed or all open activities resolved; reopens compound work and generate audit findings. 5. Reopen vs. new claim confusion — late-arriving evidence on a closed claim creates a new claim with a different number, breaking the loss-event continuity downstream finance and analytics depend on. Prerequisites A working auth + SDK layer per guidewire-install-auth and guidewire-sdk-patterns Cloud API roles cc.claim.write, cc.reserve.write, cc.payment.write assigned per least privilege; payment authorization tier matches the integration's expected payment range Knowledge of the carrier's loss-cause code list (AUTO, PROPERTY, WORKERSCOMP, etc.) and cost-category configuration (body, parts, medical, legal) A loss-dedup key strategy (typically: policyNumber + lossDate + lossCause + reporterId) Instructions 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/guidewire-core-workflow-b--3ed0cf