ideogram-upgrade-migration
Analyze, plan, and execute Ideogram SDK upgrades with breaking change detection. Use when upgrading Ideogram SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade ideogram", "ideogram migration", "ideogram breaking changes", "update ideogram SDK", "analyze ideogram version".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-upgrade-migration86
Quality
81%
Does it follow best practices?
Impact
100%
1.36xAverage score across 3 eval scenarios
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-crafted skill description that excels in completeness and distinctiveness. It provides explicit 'Use when' and 'Trigger with' clauses that make skill selection unambiguous. The main area for improvement is adding more specific concrete actions beyond general upgrade terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Ideogram SDK) and lists actions (analyze, plan, execute upgrades, breaking change detection), but the actions are somewhat general upgrade-related terms rather than highly specific concrete operations like 'generate migration scripts' or 'update deprecated method calls'. | 2 / 3 |
Completeness | Clearly answers both what (analyze, plan, execute SDK upgrades with breaking change detection) and when (explicit 'Use when...' clause with specific scenarios plus 'Trigger with phrases' providing additional guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'upgrade ideogram', 'ideogram migration', 'ideogram breaking changes', 'update ideogram SDK', 'analyze ideogram version' - these are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Ideogram SDK' as a specific product name, making it very unlikely to conflict with other skills. The combination of SDK-specific terminology and explicit trigger phrases creates a clear niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides good actionable guidance with executable code examples and clear before/after migration patterns. However, it lacks explicit validation checkpoints and error recovery steps in the workflow, and Step 4 is too vague for a potentially complex breaking change migration. The 'Error Handling' section is mislabeled (it's actually a compatibility matrix).
Suggestions
Expand Step 4 with specific validation steps: run tests, check for TypeScript errors, verify API calls work in staging before merging
Add explicit error recovery guidance: what to do if npm test fails after upgrade, how to identify which breaking changes affect the codebase
Rename 'Error Handling' section to 'Version Compatibility Matrix' for accuracy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary sections like the compatibility table under 'Error Handling' (mislabeled) and the deprecation warning boilerplate that Claude could generate on demand. | 2 / 3 |
Actionability | Provides fully executable bash commands and TypeScript code examples that are copy-paste ready, including before/after migration patterns and rollback procedures. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered but Step 4 'Handle Breaking Changes' is vague with no validation checkpoint. Missing explicit verification between npm install and declaring success; 'npm test' is mentioned but no guidance on what to do if tests fail. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate length for a single file, and references to external resources (changelog, migration guide, CI integration skill) without deep nesting. | 3 / 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.