ideogram-upgrade-migration
Migrate between Ideogram API versions (V_1 to V_2 to V3) with breaking change detection. Use when upgrading from legacy to V3 endpoints, updating model versions, or handling deprecated API parameters. Trigger with phrases like "upgrade ideogram", "ideogram migration", "ideogram v2 to v3", "ideogram breaking changes", "migrate ideogram API".
71
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that clearly defines its scope (Ideogram API version migration), provides explicit trigger guidance with natural user phrases, and occupies a very distinct niche. It uses proper third-person voice, lists concrete actions, and includes both 'Use when' and 'Trigger with' clauses for maximum discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: migrating between specific API versions (V_1, V_2, V3), breaking change detection, upgrading endpoints, updating model versions, and handling deprecated API parameters. | 3 / 3 |
Completeness | Clearly answers both 'what' (migrate between Ideogram API versions with breaking change detection) and 'when' (explicit 'Use when' clause with specific scenarios plus a 'Trigger with phrases' section listing exact trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'upgrade ideogram', 'ideogram migration', 'ideogram v2 to v3', 'ideogram breaking changes', 'migrate ideogram API'. These are realistic phrases a developer would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (Ideogram API version migration) with named versions and product-specific terminology. Extremely unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 migration guide with excellent concrete code examples, a clear breaking changes table, and a well-sequenced workflow with validation. Its main weaknesses are moderate verbosity (some sections could be trimmed or extracted to supporting files) and the monolithic structure that packs substantial code inline rather than leveraging progressive disclosure through bundle files.
Suggestions
Extract the adapter code, mapping functions, and feature flag logic into separate bundle files (e.g., adapter.ts, mappings.ts) and reference them from SKILL.md to improve progressive disclosure.
Remove the 'Output' section which merely restates what the steps already produce, and trim the 'Overview' paragraph since the breaking changes table already conveys the same information more efficiently.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code, but includes some unnecessary elements like the 'Current State' npm list command, the 'Output' section restating what was already shown, and the 'Overview' paragraph that largely repeats what the breaking changes table conveys. The feature flag rollout section adds bulk that may not be core to the migration task. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for the adapter, mapping functions, feature flags, and validation. The grep commands for auditing are copy-paste ready, the breaking changes table gives specific before/after values, and the error handling table maps specific problems to concrete solutions. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced from audit through validation, with Step 5 providing an explicit validation checkpoint that compares legacy and V3 outputs. The error handling table serves as a troubleshooting checklist, and the feature flag step provides a gradual rollout mechanism that acts as a safety net. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's a long monolithic file (~150+ lines of code) with no bundle files to offload detail. The adapter code, mapping functions, and feature flag code could be split into referenced files. The 'Next Steps' reference to 'ideogram-ci-integration' is unverifiable with no bundle. | 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
a04d1a2
- 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.