gamma-upgrade-migration
Upgrade Gamma SDK versions and migrate between API versions. Use when upgrading SDK packages, handling deprecations, or migrating to new API versions. Trigger with phrases like "gamma upgrade", "gamma migration", "gamma new version", "gamma deprecated", "gamma SDK update".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 trigger terms and clear 'what/when' guidance. Its main weakness is that the capability actions could be more specific—listing concrete migration steps rather than general verbs like 'upgrade' and 'migrate'. The Gamma SDK focus provides excellent distinctiveness.
Suggestions
Add more specific concrete actions such as 'update import paths, replace deprecated API calls, modify package versions in dependency files' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gamma SDK) and some actions (upgrade versions, migrate between API versions, handle deprecations), but doesn't list specific concrete actions like 'update import paths', 'replace deprecated method calls', or 'modify configuration files'. | 2 / 3 |
Completeness | Clearly answers both 'what' (upgrade Gamma SDK versions and migrate between API versions) and 'when' (upgrading SDK packages, handling deprecations, migrating to new API versions) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases that users would naturally say: 'gamma upgrade', 'gamma migration', 'gamma new version', 'gamma deprecated', 'gamma SDK update'. These cover common variations of how a user would request this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to 'Gamma SDK' which is a clear niche. The trigger terms all include 'gamma' as a qualifier, making it very unlikely to conflict with generic upgrade or migration 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 solid, actionable upgrade/migration skill with clear step-by-step workflow, concrete before/after code examples, and good validation checkpoints including a rollback procedure. Its main weaknesses are moderate verbosity (some unnecessary commentary and redundancy between the steps and the checklist) and the monolithic structure that could benefit from splitting detailed migration patterns into a separate file.
Suggestions
Remove the Prerequisites section and trim obvious comments (e.g., '# Node.js', '# Python') to reduce token usage—Claude already knows these contexts.
Extract the detailed v1→v2 migration patterns in Step 4 into a separate MIGRATION_PATTERNS.md file and reference it from the main skill to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary elements like the prerequisites section (Claude knows what git and test environments are) and some comments that restate the obvious. The migration patterns are useful but the overall structure could be tightened—e.g., the 'Current State' shell commands at the top and the checklist are somewhat redundant with the step-by-step instructions. | 2 / 3 |
Actionability | The skill provides fully executable bash commands and concrete TypeScript code examples showing before/after migration patterns. The rollback procedure, smoke test, and type-checking commands are all copy-paste ready with specific package names and API patterns. | 3 / 3 |
Workflow Clarity | The 7-step sequence is clearly ordered with logical progression from checking current version through testing and deprecation handling. The migration checklist provides explicit validation checkpoints, the rollback procedure addresses error recovery, and Step 6 includes both automated tests and a manual smoke test as verification. | 3 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections, but it's a fairly long monolithic file. The migration patterns (Step 4) and the detailed code examples could be split into a separate MIGRATION_PATTERNS.md file. References to external resources exist but there are no bundle files to offload detailed content to. | 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 | |
- Commit
3a2d27d
- 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.