guidewire-webhooks-events
Implement Guidewire App Events and webhook integrations for event-driven architecture. Use when setting up outbound events, message queuing, webhook receivers, or asynchronous integration patterns. Trigger with phrases like "guidewire webhooks", "app events", "event-driven", "message queue", "guidewire notifications".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill guidewire-webhooks-events84
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 distinctiveness. It explicitly provides both 'Use when' and 'Trigger with phrases' sections, making selection criteria clear. The main weakness is that the capability description could be more specific about concrete actions beyond high-level concepts like 'event-driven architecture'.
Suggestions
Add 2-3 more specific concrete actions such as 'configure event subscriptions', 'implement retry logic', or 'map event payloads to external systems' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Guidewire App Events, webhooks) and mentions some actions (outbound events, message queuing, webhook receivers), but lacks specific concrete actions like 'configure event listeners', 'set up retry policies', or 'map event payloads'. | 2 / 3 |
Completeness | Clearly answers both what (implement App Events and webhook integrations) and when (explicit 'Use when...' clause with specific scenarios plus 'Trigger with phrases' section providing additional guidance). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'guidewire webhooks', 'app events', 'event-driven', 'message queue', 'guidewire notifications'. Good coverage of both technical and common terminology. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Guidewire platform with distinct triggers like 'guidewire webhooks' and 'app events'. The Guidewire-specific terminology creates a clear niche unlikely to conflict with generic webhook or event skills. | 3 / 3 |
Total | 11 / 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 comprehensive, highly actionable skill for Guidewire event-driven integrations with excellent workflow clarity and validation checkpoints. The main weaknesses are verbosity (could trim the architecture diagram and some explanatory text) and the monolithic structure that would benefit from splitting detailed implementations into separate reference files.
Suggestions
Remove or simplify the ASCII architecture diagram - Claude understands event-driven patterns without visual aids
Move the detailed TypeScript webhook receiver and event handler implementations to a separate WEBHOOK_RECEIVER.md reference file
Move the Gosu event publisher code to a separate GOSU_EVENTS.md reference file, keeping only a brief example in the main skill
Remove the prerequisites section explaining 'understanding of event-driven architecture' - Claude already knows this
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose elements like the ASCII architecture diagram and extensive code examples that could be more condensed. The prerequisites section explains concepts Claude likely knows (event-driven architecture). | 2 / 3 |
Actionability | Provides fully executable TypeScript and Gosu code examples that are copy-paste ready. Includes complete implementations for webhook receivers, event handlers, signature verification, and monitoring with proper imports and type definitions. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence from configuration through monitoring. Includes explicit validation (signature verification, idempotency checks, replay attack prevention) and error handling with retry policies and dead-letter queues for failed events. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is monolithic at ~400 lines. The extensive code examples for webhook receiver, event handlers, Gosu publisher, and monitoring could be split into separate reference files with the main skill providing an overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (504 lines); consider splitting into references/ and linking | Warning |
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 | 8 / 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.