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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-structured with real bundle references and executable code, assuming Claude's competence throughout. Its only weakness is workflow clarity around batch/destructive operations, which lack explicit verification checkpoints.

Suggestions

Add an explicit verification checkpoint to the batch-import example, e.g. after iterating records assert the processed count matches the loaded batch size and log any skips.

For write paths (createClaim, patchResource), include a post-write validation step such as re-reading the resource to confirm the mutation landed before considering the operation complete.

Consider a short 'Verification' subsection or checklist summarizing how to confirm each of the five layers is wired correctly in production.

Dimension	Reasoning	Score
Conciseness	The body is lean for its complexity: it assumes Claude's competence (no explanation of what a checksum, retry, or REST client is) and every prose passage conveys non-obvious domain guidance such as 'retry the helper itself, not the inner PATCH'. It avoids the verbose known-concept padding that defines the score-1 anchor.	3 / 3
Actionability	Provides complete, executable TypeScript for patchResource, backoffFor, paginate, createClaim, and GwError/mapError, plus a concrete error-handling table — copy-paste ready rather than pseudocode, matching the score-3 anchor.	3 / 3
Workflow Clarity	The five numbered patterns form a clear sequence with error-recovery loops (Retry-After backoff, 409 outer-helper retry), but the batch-import example (Example 2) and write paths lack an explicit verification checkpoint, so the batch/destructive cap at 2 applies rather than 3.	2 / 3
Progressive Disclosure	SKILL.md is an overview that keeps the core patterns inline and defers deeper material to verified one-level-deep references — [implementation guide](references/implementation-guide.md) and [API reference](references/API_REFERENCE.md), both present in references/ — with a See Also section, matching the score-3 anchor.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and tightly scoped to the Guidewire Cloud API domain, with explicit what/when guidance and natural trigger terms. It matches the rubric's good examples in both voice and structure with no over-claims or padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '409 checksum conflicts on PATCH/PUT', '429 quota throttling', 'offsetToken pagination drift', 'retry-unsafe POSTs', and 'unstructured error responses' — matching the score-3 anchor of several specific concrete actions, not the partial score-2 list.	3 / 3
Completeness	Explicitly answers what ('Build a production-grade Guidewire Cloud API client that survives the request-side failures…') and when ('Use when designing an HTTP client wrapper around PolicyCenter, ClaimCenter, or BillingCenter REST endpoints') plus an explicit 'Trigger with…' clause, satisfying the score-3 anchor for both.	3 / 3
Trigger Term Quality	Trigger terms 'guidewire client', 'guidewire sdk', 'guidewire pagination', 'guidewire rate limit', 'checksum 409', and 'Retry-After' are natural phrases a Guidewire developer would actually say, giving good coverage rather than just jargon (score 2) or none (score 1).	3 / 3
Distinctiveness Conflict Risk	The Guidewire Cloud API niche is highly specific with distinct Guidewire-prefixed triggers, making it unlikely to fire for an unrelated skill; it is not the generic score-1 or overlap-prone score-2 case.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 1628598

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.