New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Ideogram Migration Deep Dive

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Plan and execute a staged migration across Ideogram legacy, V3, V4, P-Image, and tool endpoints with semantic comparison and rollback.

MITAuto-check passedDevOps & Cloud

Install Ideogram Migration Deep Dive

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ideogram-migration-deep-dive -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace ideogram-migration-deep-dive --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/ideogram-migration-deep-dive .claude/skills/ideogram-migration-deep-dive && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ideogram-migration-deep-dive
GitHub stars
2.8k
Token cost
~1.2k tokens
SKILL.md length
514 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Plan and execute a staged migration across Ideogram legacy, V3, V4, P-Image, and tool endpoints with semantic comparison and rollback.

  • Works in 7 steps: Inventory each source route, field,… → Classify every use case by required… → Select a documented target route for… → …
  • Modernizing a production image workflow
  • SKILL.md covers Overview, Prerequisites, Current Contract and Authentication, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ideogram Migration Deep Dive is an agent skill from jeremylongshore/tons-of-skills-marketplace. Plan and execute a staged migration across Ideogram legacy, V3, V4, P-Image, and tool endpoints with semantic comparison and rollback. Use when modernizing a production image workflow. Trigger with "migrate Ideogram legacy API", "move Ideogram V3 to V4", or "redesign an Ideogram image pipeline".

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; dual-run generation requires an approved cost and data plan

It sits in DevOps & Cloud. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Modernizing a production image workflow
  • With migrate Ideogram legacy API
  • Move Ideogram V3 to V4
  • Redesign an Ideogram image pipeline

Example prompts

  • “migrate Ideogram legacy API”
  • “move Ideogram V3 to V4”
  • “redesign an Ideogram image pipeline”
  • “/ideogram-migration-deep-dive”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code; dual-run generation requires an approved cost and data plan
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Inventory each source route, field, enum, output, error, retry, safety, storage, consumer, and in-flight state.
  2. Classify every use case by required model control, transparency, edit semantics, structured prompting, specialized outcome, latency, and…
  3. Select a documented target route for each use case; record non-equivalence and retire unsupported assumptions.
  4. Build owned translation at the application boundary instead of leaking mixed legacy and target schemas to consumers.
  5. Compare sanitized fixtures, then run approved shadow or dual generation into isolated storage without double publication.
  6. Evaluate transport, safety, useful quality, latency, cost, URL persistence, async reconciliation, and deletion.
  7. Canary by tenant or use case, reconcile every known generation and asset, then remove legacy traffic only after the rollback window.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code; dual-run generation requires an approved cost and data plan

    From compatibility in the SKILL.md frontmatter.

Context cost

Ideogram Migration Deep Dive loads about 1.2k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 514 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 514 words, ~1,175 tokens.

Download SKILL.mdSave it as .claude/skills/ideogram-migration-deep-dive/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
ideogram-migration-deep-dive
description
Plan and execute a staged migration across Ideogram legacy, V3, V4, P-Image, and tool endpoints with semantic comparison and rollback. Use when modernizing a production image workflow. Trigger with "migrate Ideogram legacy API", "move Ideogram V3 to V4", or "redesign an Ideogram image pipeline".
allowed-tools
Read, Glob, Grep, Write, Edit
compatibility
Designed for Claude Code; dual-run generation requires an approved cost and data plan
argument-hint
<source-surface> <target-surface> <migration-window>
version
1.11.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, ideogram, migration
model
inherit
effort
high

Ideogram Production Migration

Overview

Modernize a complete Ideogram image workflow without assuming endpoint names imply equivalent semantics. Inventory legacy and V3 behavior, select V4, P-Image, or outcome-focused tools by requirement, compare safe durable results, and preserve in-flight state and rollback.

Prerequisites

  • Source routes, payloads, traffic, consumers, stored assets, async state, quality rubric, and owners.
  • Target use cases, model-control needs, latency, safety, rights, cost, and retention constraints.
  • Feature flags, shadow destination, reconciliation plan, canary budget, and rollback window.

Current Contract

First-party navigation labels /generate, /edit, /remix, /reframe, and /describe as Legacy Endpoints. Current surfaces include V3, V4 sync/async/transparent, P-Image, edit, remix, structured describe, magic prompt, outcome-focused tools, and custom training. Payload and rendering semantics differ.

Authentication

Preserve the server-side Api-Key boundary and environment isolation throughout migration. Dual-run fixtures and receipts must exclude keys, prompts, uploaded images, generated assets, and temporary URLs.

Instructions

  1. Inventory each source route, field, enum, output, error, retry, safety, storage, consumer, and in-flight state.
  2. Classify every use case by required model control, transparency, edit semantics, structured prompting, specialized outcome, latency, and cost.
  3. Select a documented target route for each use case; record non-equivalence and retire unsupported assumptions.
  4. Build owned translation at the application boundary instead of leaking mixed legacy and target schemas to consumers.
  5. Compare sanitized fixtures, then run approved shadow or dual generation into isolated storage without double publication.
  6. Evaluate transport, safety, useful quality, latency, cost, URL persistence, async reconciliation, and deletion.
  7. Canary by tenant or use case, reconcile every known generation and asset, then remove legacy traffic only after the rollback window.

Tool Discipline

Use Read, Glob, and Grep for routes, consumers, schemas, state, and evidence. Use Write and Edit for approved migration code, tests, and records. Do not dual-run paid customer traffic or delete legacy assets by invocation alone.

Show full SKILL.md (213 more words)Show less

Approval Boundaries

Require owners for target selection, model or quality changes, dual-run spend, customer-derived content, safety differences, cutover, and destructive retirement. A migration with no state and asset reconciliation plan is not ready.

Error Handling

  • Do not map legacy enums or rendering speed by string similarity.
  • Stop on unexplained safety, output-count, aspect, storage, or quality divergence.
  • On rollback, halt target admission first and reconcile accepted target work before restoring source traffic.

Output

Return source inventory, target mapping, semantic gaps, translated contracts, fixture and shadow results, safety, quality, latency, spend, canary state, reconciled identifiers, retirement evidence, and rollback receipt.

Examples

  • Move legacy generation to V4 multipart while keeping consumer response compatibility behind an adapter.
  • Replace a broad edit flow with a specific background or reframe tool only when direct model control is unnecessary.

Validation

Run source and target contracts against the same approved synthetic cases, review visual quality separately from transport, verify durable storage and deletion, and exercise rollback under in-flight load.

Resources

  • Current first-party evidence map — use the dated endpoint, webhook, billing, team, and training links as the contract index for this workflow.
  • Recheck the endpoint-specific page and current OpenAPI description before relying on an enum, limit, beta feature, or lifecycle claim.
  • Record live observations as environment-specific evidence, not as universal vendor guarantees.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/ideogram-migration-deep-dive of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Ideogram Migration Deep Dive next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ideogram Migration Deep Dive compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ideogram Migration Deep Dive this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: PassMIT
Monitor CInrwl/nx29k6 repos~4.7kAutomated safety check: PassMIT
Terraform and OpenTofu Guideagentscope-ai/QwenPaw36k6 repos~4.2kAutomated safety check: PassApache-2.0
Vercel Optimize Auditvercel-labs/agent-skills32k8 repos~4.3kAutomated safety check: PassNone
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence
Openclaw Live Updateropenclaw/openclaw392k—~3.7kAutomated safety check: PassMIT

Similar skills

  • Monitor CI

    nrwl/nx

    Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.

    29k GitHub starsUsed in 6 repos~4.7k tokens
    DevOps & CloudAuto-check passed

  • Terraform and OpenTofu Guide

    agentscope-ai/QwenPaw

    Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.

    36k GitHub starsUsed in 6 repos~4.2k tokens
    DevOps & CloudAuto-check passed

  • Vercel Optimize Audit

    vercel-labs/agent-skills

    Official

    Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.

    32k GitHub starsUsed in 8 repos~4.3k tokens
    DevOps & CloudAuto-check passed

  • Analyze GitHub Action Logs

    withastro/astro

    Official

    Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.

    63k GitHub starsUsed in 1 repo~1.3k tokens
    DevOps & CloudAuto-check passed

  • Openclaw Live Updater

    openclaw/openclaw

    Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.

    392k GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Docs Learn PR Preview

    netdata/netdata

    Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge.

    81k GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Ideogram Migration Deep Dive

What does Ideogram Migration Deep Dive do?

Plan and execute a staged migration across Ideogram legacy, V3, V4, P-Image, and tool endpoints with semantic comparison and rollback. Ideogram Migration Deep Dive is an agent skill from jeremylongshore/tons-of-skills-marketplace. Plan and execute a staged migration across Ideogram legacy, V3, V4, P-Image, and tool endpoints with semantic comparison and rollback.

When should I use Ideogram Migration Deep Dive?

Ideogram Migration Deep Dive fits situations like: modernizing a production image workflow; with migrate Ideogram legacy API; move Ideogram V3 to V4; redesign an Ideogram image pipeline.

How do I install Ideogram Migration Deep Dive in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ideogram-migration-deep-dive -a claude-code`. Or copy the skill folder (skills/.curated/ideogram-migration-deep-dive in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/ideogram-migration-deep-dive in your project. Claude Code loads it when a task matches its description.

How do I install Ideogram Migration Deep Dive in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ideogram-migration-deep-dive -a codex`. Or copy the skill folder (skills/.curated/ideogram-migration-deep-dive in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/ideogram-migration-deep-dive in your project. Codex loads it when a task matches its description.

Can I use Ideogram Migration Deep Dive in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ideogram-migration-deep-dive -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ideogram-migration-deep-dive, .gemini/skills/ideogram-migration-deep-dive, .github/skills/ideogram-migration-deep-dive and .opencode/skills/ideogram-migration-deep-dive in your project.

What does Ideogram Migration Deep Dive need to run?

SKILL.md names no scripts, command-line tools or credentials: Ideogram Migration Deep Dive is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; dual-run generation requires an approved cost and data plan.

Does Ideogram Migration Deep Dive access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ideogram Migration Deep Dive safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ideogram Migration Deep Dive use?

Ideogram Migration Deep Dive is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ideogram Migration Deep Dive use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 619 tokens, read only when the agent opens those files.

What are the alternatives to Ideogram Migration Deep Dive?

Skills that share tags, products or a category with Ideogram Migration Deep Dive: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 36k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Analyze GitHub Action Logs (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ideogram Migration Deep Dive?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.