Agent skill · data analytics · jeremylongshore
ideogram-debug-bundle
Assemble a sanitized Ideogram support bundle with contract, status, queue, storage, and deployment evidence. Use when escalating an incident without exposing keys, prompts, images, or temporary URLs. Trigger with "build an Ideogram debug bundle", "sanitize Ideogram evidence", or "prepare an Ideogram support case".
Why this skill is useful
Adds a comprehensive executable script for collecting diagnostic information and API connectivity tests specific to the Ideogram API, which the AI wouldn't generate on its own.
What it needs
Requires curl, tar installed locally. Requires ideogram account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Ideogram Sanitized Debug Bundle Overview Create the minimum diagnostic package needed to reproduce or escalate an Ideogram problem. Preserve endpoint, schema, status, timing, concurrency, async, safety, and storage facts while excluding the content and credentials that commonly leak through generic support archives. Prerequisites An incident identifier, bounded time window, affected environment, and bundle recipient. Approved local evidence locations and a data-classification owner. A redaction policy, maximum bundle size, retention deadline, and deletion owner. Current Contract Useful content-free fields include endpoint family, method, deployment SHA, adapter version, HTTP status, sanitized vendor error class, generationid, async state, isimagesafe, URL-present boolean, queue depth, in-flight count, latency, and object-store result. Prompts, uploaded media, generated images, keys, and expiring URLs are not required by default. Authentication Represent authentication as booleans and provenance such as headerpresent=true and secretsource=production-manager. Never collect the Api-Key value, environment dumps, shell history, request headers, or secret-manager payloads. Instructions 1. Define the incident, window, recipient, evidence roots, permitted fields, byte ceiling, and deletion deadline. 2. Use an allowlist schema rather than copying full logs, requests, responses, or environment state. 3. Collect version, endpoint, status, timing, concurrency, queue, safety, polling or webhook, and storage facts. 4. Replace user, object, request, and generation identifiers with stable incident-local tokens unless the recipient explicitly requires an opaque vendor ID. 5. Scan the staged bundle for credential patterns, prompts, URLs, image signatures, EXIF, binary files, and customer identifiers. 6. Write a manifest with hashes, field provenance, redaction counts, limitations, owner, and expiry. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ideogram-debug-bundle