guidewire-sdk-patterns
Master Guidewire SDK patterns including Digital SDK, REST API Client, and Gosu best practices. Use when implementing integrations, building frontends with Jutro, or writing server-side Gosu code. Trigger with phrases like "guidewire sdk", "digital sdk", "jutro sdk", "guidewire patterns", "gosu best practices", "rest api client".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill guidewire-sdk-patterns83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%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 a well-structured skill description with strong completeness and excellent trigger term coverage for the Guidewire ecosystem. The main weakness is that the capabilities could be more specific - listing concrete actions rather than general categories like 'implementing integrations'. The description effectively carves out a distinct niche that won't conflict with other skills.
Suggestions
Replace general phrases like 'implementing integrations' with specific actions such as 'configure REST endpoints', 'handle authentication flows', or 'implement data transformations'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Guidewire SDK) and mentions some actions like 'implementing integrations', 'building frontends with Jutro', and 'writing server-side Gosu code', but these are somewhat general rather than listing multiple concrete specific actions like 'create API endpoints' or 'configure authentication'. | 2 / 3 |
Completeness | Clearly answers both what ('Master Guidewire SDK patterns including Digital SDK, REST API Client, and Gosu best practices') and when ('Use when implementing integrations, building frontends with Jutro, or writing server-side Gosu code') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'guidewire sdk', 'digital sdk', 'jutro sdk', 'guidewire patterns', 'gosu best practices', 'rest api client'. Good coverage of domain-specific terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Guidewire ecosystem with distinct triggers like 'Jutro', 'Gosu', 'Digital SDK' that are unlikely to conflict with other skills. Clear niche in enterprise insurance software development. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive SDK patterns skill with excellent actionability through complete, executable code examples across frontend, integration, and server-side patterns. The main weaknesses are moderate verbosity in some sections and missing validation checkpoints for multi-step setup processes like SDK generation and client configuration.
Suggestions
Add validation steps after SDK generation (e.g., 'Verify SDK generated correctly: check src/sdk/account.ts exists and contains useAccount export')
Trim explanatory headers like 'Master the key SDK patterns' - the section structure already conveys this
Add a verification step after REST API Client gradle setup to confirm successful generation before using the client
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanatory text like 'Master the key SDK patterns' and verbose comments. The code examples are substantial but could be tightened in places. | 2 / 3 |
Actionability | Excellent actionability with fully executable code examples across all three SDK patterns. Commands are copy-paste ready (npx commands, gradle config), and code snippets are complete with imports and proper structure. | 3 / 3 |
Workflow Clarity | While individual code patterns are clear, the skill lacks explicit validation checkpoints. For SDK generation and integration setup, there are no verification steps to confirm success before proceeding. The transaction patterns mention rollback but don't show explicit validation workflows. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Digital SDK, REST API Client, Gosu Patterns). References to external resources and next steps are one level deep and clearly signaled. Prerequisites point to related skills appropriately. | 3 / 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 | |
- 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.