Agent skill · software engineering · jeremylongshore
ideogram-common-errors
Diagnose Ideogram authentication, validation, throttling, capacity, safety, and asset-expiry failures by evidence class. Use when a request fails or returns no usable image. Trigger with "debug Ideogram 422", "fix Ideogram 429", or "diagnose an empty Ideogram URL".
Why this skill is useful
Provides specific troubleshooting scripts and patterns for handling Ideogram API errors that the AI wouldn't reliably generate on its own.
What it needs
Requires curl installed locally. Requires ideogram account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Ideogram Error Diagnosis Overview Classify an Ideogram failure before changing code or retrying spend. Separate authentication, billing readiness, request validation, throttling, service capacity, safety policy, asynchronous lifecycle, download expiry, and application storage failures. Prerequisites Endpoint, method, environment, timestamp, sanitized status, and opaque request or generation identifier. The exact adapter version and current endpoint documentation. Access to content-free logs, fixtures, queue state, and storage receipts. Current Contract Endpoint docs surface 400, 401, 422, and 429; operational paths can also encounter transient service failures such as 503. V4 FLASH currently produces 400. Unsafe generation may complete with isimagesafe=false and an empty URL. Async work must reach a recognized terminal state. Authentication Verify only that a server-side Api-Key header is configured for https://api.ideogram.ai; never paste or print its value. A key, team balance, and application user authorization are separate checks. Instructions 1. Capture the endpoint, status, latency, attempt count, content type, sanitized error code, and opaque identifiers. 2. Reproduce against a fixture before considering another paid live call. 3. Map 401 to key presence, header name, environment, and revocation; map 400 or 422 to endpoint-specific fields and media validation. 4. Map 429 to local in-flight concurrency, queue deadline, and server retry guidance; map 503 or transport failure to bounded transient handling. 5. Inspect isimagesafe, URL presence, async terminal state, download timing, and durable-storage result separately. 6. Apply one minimal correction, rerun the deterministic test, and use one approved synthetic live probe only if needed. 7. Record cause, evidence, spend, affected scope, correction, and rollback. Tool Discipline Use Read, Glob, and Grep for adapters, schemas, logs, and fixtures. Use Write and Edit only for an approved minimal fix or test. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ideogram-common-errors--bafb2d