CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable migration guide with executable code, clear sequencing, and validation. Its only real weakness is progressive disclosure: everything lives in one ~200-line file with no bundle files to defer detail to.

Suggestions

Move the full adapter (generateLegacy/generateV3) and enum-mapping tables into a scripts/ or references/ file, keeping SKILL.md as an overview that links to them.

Add a short 'Quick start' summary at the top so the core migration path is visible before the full code blocks.

Consider extracting the V3-exclusive feature list and error-handling table into a reference doc linked from the body.

DimensionReasoningScore

Conciseness

The body is lean: a one-paragraph overview plus dense tables and executable code, with no padding explaining concepts Claude already knows. Not a 2 because every section earns its tokens.

3 / 3

Actionability

Provides copy-paste-ready TypeScript (adapter, enum maps, feature flag), concrete grep audit commands, and a validation script — fully executable, not pseudocode.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced (Audit → Adapter → Map Enums → Feature Flag → Validate), with an explicit validation step (validateMigration) and an Error Handling table for recovery. Not capped at 2 because the migration is not a destructive/batch operation and validation is present.

3 / 3

Progressive Disclosure

Sections are well-organized, but the skill is ~200 lines with all content inline and no bundle files (references/scripts/assets are absent) to offload the full adapter or enum maps into. Not a 3 because content that could be split out remains monolithic; not a 1 because structure and one-level external links exist.

2 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states capabilities, use cases, and natural trigger phrases with no fluff. It answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: "Migrate between Ideogram API versions", "breaking change detection", "upgrading from legacy to V3 endpoints", "updating model versions", and "handling deprecated API parameters".

3 / 3

Completeness

Explicitly answers what (migrate versions with breaking-change detection) and when ("Use when upgrading from legacy to V3 endpoints, updating model versions, or handling deprecated API parameters") with explicit trigger phrases.

3 / 3

Trigger Term Quality

Provides natural phrases a user would actually say: "upgrade ideogram", "ideogram migration", "ideogram v2 to v3", "ideogram breaking changes", "migrate ideogram API".

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to the Ideogram API with version-specific triggers ("ideogram v2 to v3"), making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.