guidewire-sdk-patterns

Master Guidewire SDK patterns: REST API Client, Jutro Digital SDK, and Gosu best practices. Trigger: "guidewire sdk patterns", "sdk-patterns".

Quality

36%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/saas-packs/guidewire-pack/skills/guidewire-sdk-patterns/SKILL.md

Quality

Discovery

50%

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 identifies a specific technology domain (Guidewire SDK) and names three sub-areas, which provides some useful specificity. However, it lacks concrete action verbs describing what the skill actually does, and the trigger guidance is limited to literal keyword strings rather than natural user language or scenario-based 'Use when...' clauses. The word 'Master' is aspirational rather than descriptive of capabilities.

Suggestions

Replace 'Master' with concrete action verbs describing what the skill does, e.g., 'Implements REST API clients, builds Jutro Digital UI components, and writes idiomatic Gosu code for Guidewire platforms.'

Add a 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user asks about Guidewire integration, building ClaimCenter/PolicyCenter extensions, Jutro UI components, Gosu language syntax, or Guidewire REST API calls.'

Include more natural keyword variations users might say, such as 'Gosu language', 'Jutro components', 'ClaimCenter', 'PolicyCenter', 'BillingCenter', or 'Guidewire Cloud API'.

Dimension	Reasoning	Score
Specificity	Names the domain (Guidewire SDK) and lists some specific areas (REST API Client, Jutro Digital SDK, Gosu best practices), but doesn't describe concrete actions like 'implement', 'configure', or 'debug'. 'Master' is vague and not an actionable verb.	2 / 3
Completeness	The 'what' is partially addressed (SDK patterns for REST API, Jutro, Gosu), but the 'when' is only provided as literal trigger strings rather than describing scenarios when Claude should select this skill. There's no 'Use when...' clause with natural usage contexts.	2 / 3
Trigger Term Quality	Includes some relevant keywords like 'REST API Client', 'Jutro Digital SDK', 'Gosu', and 'guidewire sdk patterns', but misses natural user phrases like 'Guidewire API', 'Gosu language', 'Jutro components', 'ClaimCenter SDK', or 'PolicyCenter integration'.	2 / 3
Distinctiveness Conflict Risk	The Guidewire domain is fairly niche which helps distinctiveness, but 'REST API Client' and 'best practices' are generic enough to potentially overlap with other API or coding skills. The description doesn't clearly delineate its boundary from a general Guidewire skill or a general REST API skill.	2 / 3
	Total	8 / 12 Passed

Implementation

22%

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

This skill is essentially a stub: it names three SDK areas and defers all actual content to a reference file and external links. There are no code examples, no concrete patterns, no workflows, and no actionable guidance in the skill body itself. The structure hints at progressive disclosure but fails because the top-level content is too thin to be useful on its own.

Suggestions

Add at least one concrete, executable code example for each of the three patterns (REST API Client, Jutro SDK, Gosu) directly in the SKILL.md body as a quick-start section.

Include a brief workflow or step sequence for a common task (e.g., making a REST API call with the GW client library) with validation/error handling steps.

Provide specific, copy-paste-ready code snippets rather than abstract descriptions like 'Use GW REST API Client library for type-safe API calls'.

Ensure the SKILL.md has enough standalone content to be useful even without clicking through to the implementation guide — the overview should contain actionable patterns, not just topic labels.

Dimension	Reasoning	Score
Conciseness	The content is brief but the overview paragraph reads more like a description than actionable instruction. It's not verbose, but it doesn't earn every token either — the overview sentence is somewhat vague and could be tighter.	2 / 3
Actionability	There is no concrete code, no executable examples, no specific commands or patterns. The skill describes what to use (REST API Client, Jutro, Gosu) but never shows how. Everything is deferred to a reference file or external links.	1 / 3
Workflow Clarity	There are no steps, no sequences, no workflows described at all. For a skill covering multiple SDK patterns (REST client, Jutro, Gosu), there should be at least a basic workflow or usage pattern for each, but none are provided.	1 / 3
Progressive Disclosure	There is a reference to an implementation guide and external resources, which is good structure. However, the SKILL.md itself provides almost no substantive quick-start content — it's essentially just a pointer with no usable overview content to stand on its own.	2 / 3
	Total	6 / 12 Passed

Validation

81%

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 — 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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3e83543

Reviewed: 3 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.