guidewire-upgrade-migration
Upgrade Guidewire InsuranceSuite versions and migrate between environments. Use when planning version upgrades, handling breaking changes, or migrating from self-managed to Cloud. Trigger with phrases like "guidewire upgrade", "version migration", "insurancesuite update", "cloud migration", "upgrade path".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill guidewire-upgrade-migration85
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 excellent trigger term coverage and completeness. It clearly identifies when to use the skill and provides explicit trigger phrases. The main weakness is that the specific capabilities could be more detailed - 'upgrade versions' and 'migrate between environments' are somewhat general actions that could benefit from more concrete sub-actions.
Suggestions
Add more specific concrete actions like 'analyze upgrade compatibility', 'generate migration scripts', 'identify deprecated APIs', or 'map configuration differences between versions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Guidewire InsuranceSuite) and some actions (upgrade versions, migrate between environments), but lacks comprehensive specific actions like 'handle breaking changes' which is mentioned but vague, and doesn't detail what migration or upgrade steps actually involve. | 2 / 3 |
Completeness | Clearly answers both what (upgrade versions, migrate environments) and when (explicit 'Use when' clause with planning upgrades, handling breaking changes, migrating to Cloud, plus explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'guidewire upgrade', 'version migration', 'insurancesuite update', 'cloud migration', 'upgrade path' - these are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific product name (Guidewire InsuranceSuite) and specialized domain (insurance software upgrades/migrations). Very unlikely to conflict with other skills due to the niche technical focus. | 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 strong, actionable skill with excellent workflow clarity and concrete executable examples for Guidewire upgrades. The 7-step process with validation checkpoints and rollback procedures demonstrates good engineering practices. However, the skill could benefit from moving detailed code examples to separate reference files to improve progressive disclosure and reduce token usage.
Suggestions
Move detailed code examples (TypeScript interfaces, full Gosu classes) to separate reference files like MIGRATION-SCRIPTS.md and link to them from the main skill
Remove explanatory code comments that describe what the code does (e.g., '// Replace deprecated API calls') since Claude can infer this from context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose elements like the full TypeScript interface definitions and extensive code comments that could be tightened. The tables and checklists are efficient, but some scripts include explanatory comments Claude doesn't need. | 2 / 3 |
Actionability | Provides fully executable bash scripts, Gradle tasks, Gosu code, and TypeScript examples that are copy-paste ready. Each step has concrete commands and code rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | Clear 7-step sequence with explicit validation checkpoints (Step 3 includes validateDatabaseUpgrade, Step 7 is dedicated testing). Includes rollback procedure and checklists for complex cloud migration with status tracking. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is quite long (~300 lines) with detailed code that could be split into separate reference files. The 'Next Steps' and 'Resources' sections provide good navigation, but inline code density is high. | 2 / 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.