Agent skill · software engineering · jeremylongshore
guidewire-sdk-patterns
Build a production-grade Guidewire Cloud API client that survives the request-side failures — 409 checksum conflicts on PATCH/PUT, 429 quota throttling, offsetToken pagination drift, retry-unsafe POSTs, and unstructured error responses. Use when designing an HTTP client wrapper around PolicyCenter, ClaimCenter, or BillingCenter REST endpoints. Trigger with "guidewire client", "guidewire sdk", "checksum 409", "guidewire pagination", "guidewire rate limit", "Retry-After".
Why this skill is useful
Adds a comprehensive production-grade API client implementation with specific patterns for handling Guidewire Cloud API failures, including executable code for safe mutations and error handling.
What it needs
Requires node installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Guidewire SDK Patterns Overview Build the Cloud API request layer that runs in production. This skill assumes the auth layer from guidewire-install-auth is in place — bearer tokens come from the cached token provider, not a static APIKEY. What this layer adds: safe mutations under optimistic locking, retry-aware writes, quota-friendly request pacing, complete pagination, and a typed error surface that business logic can pattern-match. Five production failures this skill prevents: 1. 409 Conflict storms — client GETs a record, lets the user (or workflow) edit it, then PATCHes back without the latest checksum; the next concurrent edit causes both PATCHes to lose. 2. 429 cascades — every retry on 429 happens at the same backoff, all clients hammer the endpoint together, the tenant rate quota stays pinned. 3. Silent data loss in pagination — client treats pageSize=100 as "all results"; misses page 2 onward; reports inflated coverage to downstream. 4. Duplicate writes on retry — POST to create-claim times out at the load balancer, client retries, two claims land with the same FNOL. 5. Generic error handling — every non-2xx response collapses into "request failed", losing the userMessage, errors[].type, and attributes structure the API actually returns. Prerequisites A working auth layer per guidewire-install-auth — getToken() returning a cached, scope-validated bearer Cloud API endpoints reachable on [TENANT].guidewire.net (PC/CC/BC base URLs in env) Node 20+ or equivalent runtime supporting fetch, AbortController, and crypto.randomUUID Familiarity with the Cloud API response envelope (data[], attributes, checksum, links) — see guidewire-install-auth/references/APIREFERENCE.md Instructions Implement the patterns below as composable layers on top of fetch. Each pattern targets one of the five production failures listed in Overview; do not skip any layer in production code. 1. Checksum round-trip for safe mutations Every Cloud API resource carries a checksum. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/guidewire-sdk-patterns