CtrlK
BlogDocsLog inGet started
Tessl Logo

guidewire-core-workflow-b

Automate the ClaimCenter FNOL→investigation→reserve→payment→settlement→close pipeline including the failure paths — duplicate FNOL from multi-source intake, reserve-must-precede-payment ordering, supervisor-authorization tiers, premature settlement, and reopen-vs-new-claim ambiguity. Use when building claim intake from caller portals, IVR, or partner systems; automating reserve-setting jobs; or integrating settlement events with finance. Trigger with "claimcenter automation", "FNOL", "claim reserve", "claim payment", "claim settlement", "claim reopen".

78

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tightly written, executable workflow guide: it sequences the claim lifecycle with real Cloud API code, gates risky closure behind an explicit readiness check, and pushes deeper detail to real reference files. It avoids explaining concepts Claude already knows while surfacing non-obvious domain failure modes.

DimensionReasoningScore

Conciseness

Dense, domain-specific body that assumes Claude's competence (no basic explanation of claims/reserves/HTTP) and keeps every section load-bearing — the 'Five production failures' framing is genuine domain knowledge, not filler — fitting the lean/efficient score-3 anchor.

3 / 3

Actionability

Provides fully executable TypeScript with real endpoints, auth headers, idempotency keys, request bodies, and status handling across all five steps, plus a concrete error table with causes and fixes — copy-paste-ready per the score-3 anchor.

3 / 3

Workflow Clarity

A clearly sequenced five-step lifecycle (FNOL→reserve→payment→settlement→reopen) with an explicit validation gate — isReadyToSettle() must return ready:true before close — and error-table feedback loops (e.g., reserve POST first, then retry payment), matching the score-3 anchor for sequence plus validation and recovery.

3 / 3

Progressive Disclosure

SKILL.md is an overview with the core workflow inline and deeper topics offloaded to verified one-level-deep references — references/implementation-guide.md and references/API_REFERENCE.md — alongside See Also and Resources sections, satisfying the clear-overview-with-well-signaled-references score-3 anchor.

3 / 3

Total

12

/

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 distinctive: it names the exact pipeline and failure paths, provides explicit 'Use when' guidance, and includes natural trigger terms. Voice is third-person with no first/second-person phrasing to penalize.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — automating the FNOL→…→close pipeline — and enumerates specific failure paths (duplicate FNOL, reserve-before-payment, authorization tiers, premature settlement, reopen-vs-new-claim), matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Clearly answers both 'what' (the lifecycle pipeline and its failure modes) and 'when' ('Use when building claim intake from caller portals, IVR, or partner systems…'), plus explicit triggers, satisfying the score-3 anchor for what AND when with explicit triggers.

3 / 3

Trigger Term Quality

An explicit 'Trigger with' clause supplies natural phrases a user would say — 'claimcenter automation', 'FNOL', 'claim reserve', 'claim payment', 'claim settlement', 'claim reopen' — giving good coverage of natural terms rather than just jargon.

3 / 3

Distinctiveness Conflict Risk

Highly niche ClaimCenter claims-lifecycle scope with named failure modes and distinct trigger phrases, making it unlikely to fire for unrelated skills per the score-3 anchor.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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