CtrlK
BlogDocsLog inGet started
Tessl Logo

ideogram-migration-deep-dive

Migrate from other image generation APIs to Ideogram, or re-architect existing Ideogram integrations. Use when switching from DALL-E/Midjourney/Stable Diffusion to Ideogram, or performing major integration overhauls. Trigger with phrases like "migrate to ideogram", "switch to ideogram", "replace dall-e with ideogram", "ideogram replatform", "ideogram migration".

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/ideogram-pack/skills/ideogram-migration-deep-dive/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

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

A thorough, actionable migration guide with executable code and a clear sequenced workflow. Its weak spots are progressive disclosure (no real bundle files, a broken reference) and minor conciseness redundancy.

Suggestions

Add an actual reference file for the advanced/debug material and replace the dangling "ideogram-debug-bundle" pointer with a real path, or remove the reference.

Deduplicate the Ideogram advantages (Overview vs. "Ideogram Advantages Post-Migration") and consolidate the parameter mapping into a single place to trim tokens.

Define DallEProvider (or note it as the user's existing provider) and add a brief V3 FormData example to close the actionability gaps.

DimensionReasoningScore

Conciseness

The body is mostly efficient code and tables, but Ideogram advantages are listed in both the Overview and a dedicated post-migration section, and parameter mapping appears both as before/after code and a full table, which could be trimmed.

4 / 5

Actionability

It provides concrete, mostly copy-paste-ready TypeScript (adapter, feature-flag split, validation), but references an undefined DallEProvider and mentions a V3 FormData path in the table without giving an example.

4 / 5

Workflow Clarity

The six steps (Audit, API Mapping, Parameter Mapping, Adapter, Feature-Flag Rollout, Validation) are clearly sequenced with a validation step and error-handling table, but an explicit "fix then re-validate" retry loop is not spelled out.

4 / 5

Progressive Disclosure

Sections are well-organized, but the skill is monolithic with no bundle files, the full adapter code and parameter tables are inlined rather than split out, and the Next Steps reference to "ideogram-debug-bundle" points to a non-existent file.

3 / 5

Total

15

/

20

Passed

Description

82%Weight 40%Scale 1-5

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 description with clear what/when framing and concrete trigger phrases targeting a well-defined niche. The main weakness is specificity, where the action verbs are limited and somewhat generic.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions ("Migrate from other image generation APIs to Ideogram, or re-architect existing Ideogram integrations"), but the verbs are generic and coverage is not comprehensive.

3 / 5

Completeness

It explicitly answers both what (migrate/re-architect to Ideogram) and when ("Use when switching from DALL-E/Midjourney/Stable Diffusion to Ideogram"), reinforced by concrete trigger phrases.

5 / 5

Trigger Term Quality

It lists several natural trigger phrases ("migrate to ideogram", "switch to ideogram", "replace dall-e with ideogram", "ideogram migration") with synonyms, though a few natural variations are missing and "ideogram replatform" leans jargon-y.

4 / 5

Distinctiveness Conflict Risk

The Ideogram-migration niche is specific with distinct, provider-named triggers, giving minimal overlap risk with other skills.

5 / 5

Total

17

/

20

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.