guidewire-reference-architecture
Enterprise reference architecture for Guidewire InsuranceSuite Cloud deployments. Use when designing system architecture, planning integrations, or understanding Guidewire cloud infrastructure patterns. Trigger with phrases like "guidewire architecture", "system design", "integration architecture", "enterprise guidewire", "reference architecture".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill guidewire-reference-architecture70
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 clearly identifies its niche (Guidewire InsuranceSuite Cloud) and provides explicit trigger phrases. The main weakness is that the capabilities described are somewhat abstract ('designing system architecture', 'planning integrations') rather than listing specific concrete deliverables or actions the skill enables.
Suggestions
Add specific concrete actions like 'create deployment diagrams', 'define integration patterns', 'document security architecture', or 'generate infrastructure specifications' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Guidewire InsuranceSuite Cloud) and general actions (designing architecture, planning integrations, understanding patterns), but lacks specific concrete actions like 'create deployment diagrams', 'configure API gateways', or 'define security boundaries'. | 2 / 3 |
Completeness | Clearly answers both what (enterprise reference architecture for Guidewire InsuranceSuite Cloud deployments) and when (designing system architecture, planning integrations, understanding cloud infrastructure patterns) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'guidewire architecture', 'system design', 'integration architecture', 'enterprise guidewire', 'reference architecture'. These are realistic terms for the target domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific 'Guidewire InsuranceSuite Cloud' domain focus. The combination of 'guidewire' with architecture terms creates a clear niche unlikely to conflict with generic architecture or other enterprise software skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference architecture document with good visual diagrams and comprehensive coverage of Guidewire cloud patterns. However, it leans heavily toward descriptive content rather than actionable guidance, and the monolithic structure makes it harder to navigate. The content would benefit from more executable examples and clearer separation of concerns into linked reference files.
Suggestions
Add more executable code examples for each integration pattern, showing actual API calls or configuration files that can be directly used
Split detailed sections (Security Architecture, Scalability Patterns, Integration Patterns) into separate linked reference files to improve progressive disclosure
Remove the Prerequisites section - Claude already understands enterprise architecture and cloud concepts
Add validation checkpoints to the data flow sections, such as 'verify policy data integrity before proceeding to binding' with specific checks to perform
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is comprehensive but includes some unnecessary verbosity, such as the prerequisites section explaining concepts Claude would already know. The YAML data flow sections could be more compact, and some diagrams repeat information. | 2 / 3 |
Actionability | Provides good architectural diagrams and one TypeScript code example, but most content is descriptive rather than executable. The YAML configurations are illustrative but not directly usable without significant context. Missing concrete implementation steps for actually deploying or configuring these patterns. | 2 / 3 |
Workflow Clarity | Data flows are documented with numbered steps, but there are no validation checkpoints or error recovery guidance. For an architecture reference, the deployment and integration patterns lack explicit verification steps or decision points for when things go wrong. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but it's a monolithic document that could benefit from splitting detailed patterns (security, scaling, integration) into separate reference files. The single 'Next Steps' link is good but more cross-references would improve navigation. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 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.