Individual skill

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

plugins/saas-packs/ideogram-pack/skills/ideogram-common-errors/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,916
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# 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 `is_image_safe=false` and an empty URL. Async work must reach a recognized terminal state.
Back to top