guidewire-upgrade-migration
Upgrade Guidewire InsuranceSuite versions and migrate between Cloud environments. Trigger: "guidewire upgrade migration", "upgrade-migration".
50
40%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/guidewire-pack/skills/guidewire-upgrade-migration/SKILL.mdQuality
Discovery
57%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 targets a clear niche (Guidewire InsuranceSuite upgrades and cloud migrations), which gives it strong distinctiveness. However, it lacks specificity about concrete actions performed during upgrades/migrations and does not include an explicit 'Use when...' clause. The trigger terms are limited and could benefit from more natural language variations.
Suggestions
Add a 'Use when...' clause describing specific scenarios, e.g., 'Use when upgrading Guidewire InsuranceSuite from one version to another, migrating between Cloud environments, or handling schema/configuration changes during version transitions.'
Expand trigger terms with natural variations users might say, such as 'version upgrade', 'cloud migration', 'InsuranceSuite upgrade', 'environment migration', 'Guidewire version bump', or specific version references.
List more specific concrete actions, e.g., 'Updates configuration files, migrates database schemas, resolves API compatibility issues, and validates environment settings during Guidewire InsuranceSuite version upgrades and Cloud environment migrations.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Guidewire InsuranceSuite) and two actions (upgrade versions, migrate between Cloud environments), but lacks detail on what specific steps or sub-actions are involved (e.g., schema migration, configuration updates, compatibility checks). | 2 / 3 |
Completeness | The 'what' is partially addressed (upgrade and migrate), and there is a trigger line, but it lacks an explicit 'Use when...' clause describing the scenarios or conditions under which this skill should be selected. The trigger terms are listed but not framed as usage guidance. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'guidewire upgrade migration' and 'upgrade-migration', but misses natural variations users might say such as 'version upgrade', 'cloud migration', 'InsuranceSuite migration', 'environment migration', or specific version names. | 2 / 3 |
Distinctiveness Conflict Risk | Guidewire InsuranceSuite is a very specific enterprise product, making this skill highly distinctive and unlikely to conflict with other skills. The niche domain creates clear differentiation. | 3 / 3 |
Total | 9 / 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 placeholder rather than actionable guidance. It provides a one-sentence summary of the upgrade process with no concrete steps, commands, validation checkpoints, or examples. The reference to an implementation guide suggests content may exist elsewhere, but the SKILL.md itself fails to provide enough information for Claude to act on confidently.
Suggestions
Add a numbered, multi-step workflow with explicit validation checkpoints (e.g., 'Run upgrade tool: `gw upgrade --version X.Y.Z`', 'Validate Gosu compilation: `gw test compile`', 'If errors: fix and re-validate before proceeding').
Include at least one concrete, executable code or command example for key steps like running the upgrade tool, checking API compatibility, or promoting through environments.
Add a validation/verification feedback loop for the upgrade process, especially around configuration merging and Gosu customization testing, since these are potentially destructive operations.
Expand the overview to include enough actionable detail that Claude can begin work without needing to immediately defer to the implementation guide.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief and doesn't over-explain concepts Claude already knows, but the overview reads more like a compressed checklist than lean, purposeful instruction. It's efficient in length but not in utility per token. | 2 / 3 |
Actionability | The skill provides no concrete commands, code examples, or executable steps. The overview is a vague summary of activities ('run upgrade tool', 'merge configuration changes') without specifying how to do any of them. It describes rather than instructs. | 1 / 3 |
Workflow Clarity | The overview lists activities in a single sentence without clear sequencing, numbered steps, validation checkpoints, or error recovery. For a multi-step upgrade/migration process involving destructive and batch operations, this is critically insufficient. | 1 / 3 |
Progressive Disclosure | There is a reference to an implementation guide and external resources, which shows some progressive disclosure structure. However, the overview itself is too thin to serve as a useful entry point, and it's unclear what the referenced implementation guide actually contains or how it's organized. | 2 / 3 |
Total | 6 / 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 | |
- Commit
70e9fa4
- 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.