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".
71
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is an excellent skill description that excels across all dimensions. It provides highly specific capabilities tied to concrete failure modes, includes explicit 'Use when' and 'Trigger with' clauses, and occupies a very distinct niche around Guidewire Cloud API integration. The description uses proper third-person voice and avoids vague language or buzzwords.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and failure modes: 409 checksum conflicts on PATCH/PUT, 429 quota throttling, offsetToken pagination drift, retry-unsafe POSTs, and unstructured error responses. Very detailed about what the skill handles. | 3 / 3 |
Completeness | Clearly answers both 'what' (build a production-grade Guidewire Cloud API client handling specific failure modes) and 'when' (explicit 'Use when' clause for designing HTTP client wrappers around Guidewire REST endpoints, plus explicit 'Trigger with' terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'guidewire client', 'guidewire sdk', 'checksum 409', 'guidewire pagination', 'guidewire rate limit', 'Retry-After', plus domain-specific terms like PolicyCenter, ClaimCenter, BillingCenter that users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely niche and distinctive — targets Guidewire Cloud API specifically with domain-specific terminology (PolicyCenter, ClaimCenter, BillingCenter, offsetToken pagination, checksum 409). Very unlikely to conflict with generic HTTP client or API skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, production-focused skill with excellent actionability — every pattern includes executable TypeScript targeting real Guidewire Cloud API conventions. The workflow clarity is outstanding with explicit feedback loops for 409 retries and a comprehensive error handling decision table. The main weaknesses are moderate verbosity in explanatory sections and references to bundle files that don't exist, which undermines progressive disclosure claims.
Suggestions
Trim the Overview section — the five-failure list is valuable but the explanations could be condensed to one line each since Claude understands HTTP error semantics.
Provide the referenced bundle files (references/implementation-guide.md, references/API_REFERENCE.md) or remove the references to avoid dead links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The overview section listing five production failures is useful context but somewhat verbose. The prerequisites and some explanatory prose (e.g., explaining what checksum is, what 429 means) could be trimmed since Claude knows HTTP semantics. However, the Guidewire-specific details earn their place. Overall mostly efficient with some tightening possible. | 2 / 3 |
Actionability | Every pattern includes fully executable TypeScript code with concrete function signatures, proper headers, JSON body structures, and real API paths. The examples are copy-paste ready and cover the exact Guidewire Cloud API conventions (checksum in body, links.next.href pagination, Idempotency-Key header). | 3 / 3 |
Workflow Clarity | The five patterns are clearly sequenced and each addresses a specific failure mode. The checksum round-trip explicitly states to retry the outer helper not the inner PATCH. The error handling table provides a comprehensive decision matrix with cause → solution mappings. The 409 retry feedback loop is explicitly documented. | 3 / 3 |
Progressive Disclosure | The skill references `references/implementation-guide.md` and `references/API_REFERENCE.md` but no bundle files are provided, so these references are unverifiable. The See Also section links to related skills appropriately. However, the inline content is quite long (~200+ lines) and some sections like the full error handling table could potentially be split out. The structure is good but the skill is somewhat monolithic for its length. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
a04d1a2
- Reviewed
Table of Contents
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.