Skip to main content
ideogram-debug-bundle Collect Ideogram debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Ideogram problems.
Trigger with phrases like "ideogram debug", "ideogram support bundle",
"collect ideogram logs", "ideogram diagnostic".
Zur Installation springen Skills Marktplatz Entdecken und erkunden Sie KI-Skills, die von der Community erstellt wurden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Prompt kopierenPrompt-Details anzeigen Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-debug-bundleDer Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.
Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.
ZIP herunterladen Herunterladen... Verwandte Berufe SOC
Basierend auf der SOC-Berufsklassifikation
Mehr aus diesem Repository Implement user sign-up and sign-in flows with Clerk.
Use when building authentication UI, customizing sign-in experience,
or implementing OAuth social login.
Trigger with phrases like "clerk sign-in", "clerk sign-up",
"clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk.
Use when managing user sessions, configuring route protection,
or implementing token refresh and custom JWT templates.
Trigger with phrases like "clerk session", "clerk middleware",
"clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management.
Use when implementing SSO integration, configuring role-based permissions,
or setting up organization-level controls.
Trigger with phrases like "clerk SSO", "clerk RBAC",
"clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
name ideogram-debug-bundle description Collect Ideogram debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Ideogram problems.
Trigger with phrases like "ideogram debug", "ideogram support bundle",
"collect ideogram logs", "ideogram diagnostic".
allowed-tools Read, Bash(curl:*), Bash(tar:*), Bash(node:*), Grep version 1.10.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","ideogram","debugging","support"] compatibility Designed for Claude Code, also compatible with Codex and OpenClaw
Ideogram Debug Bundle
Current State
!node --version 2>/dev/null || echo 'N/A'
!python3 --version 2>/dev/null || echo 'N/A'
!echo "IDEOGRAM_API_KEY set: ${IDEOGRAM_API_KEY:+YES}${IDEOGRAM_API_KEY:-NO}"
Overview
Collect diagnostic information for Ideogram API issues. Produces a tarball with environment details, API connectivity tests, request/response samples, and redacted configuration -- suitable for attaching to support tickets.
Prerequisites
IDEOGRAM_API_KEY environment variable set
curl and tar available
Permission to collect environment info
Instructions
Step 1: Full Debug Bundle Script
#!/bin/bash
set -euo pipefail
BUNDLE_DIR="ideogram-debug-$(date +%Y%m%d-%H%M%S) "
mkdir -p "$BUNDLE_DIR "
cat > "$BUNDLE_DIR /summary.txt" <<HEADER
=== Ideogram Debug Bundle ===
Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ)
Hostname: $(hostname)
HEADER
{
echo "--- Runtime ---"
echo "Node: $(node --version 2>/dev/null || echo 'not installed') "
echo "Python: $(python3 --version 2>/dev/null || echo 'not installed') "
echo "OS: $(uname -srm) "
echo ""
echo "--- Ideogram Config ---"
echo "API Key: ${IDEOGRAM_API_KEY:+SET (length=${#IDEOGRAM_API_KEY} )} ${IDEOGRAM_API_KEY:-NOT SET} "
} >>
{
RESPONSE=$(curl -s -w \
-X POST https://api.ideogram.ai/generate \
-H \
-H \
-d \
2>&1 || )
| grep -E ||
| -5 >
} >>
{
} >>
[ -f . ];
sed . >
{
npm list --depth=0 2>/dev/null ||
pip freeze 2>/dev/null | grep -i ideogram ||
} >>
tar -czf
-rf
"$BUNDLE_DIR /summary.txt"
echo
""
echo
"--- API Test (Legacy Generate) ---"
"\nHTTP_STATUS:%{http_code}\nTIME_TOTAL:%{time_total}"
"Api-Key: ${IDEOGRAM_API_KEY:-missing} "
"Content-Type: application/json"
'{"image_request":{"prompt":"debug test","model":"V_2_TURBO","magic_prompt_option":"OFF"}}'
echo
"CURL_FAILED"
echo
"$RESPONSE "
"HTTP_STATUS|TIME_TOTAL|error"
true
echo
"$RESPONSE "
head
"$BUNDLE_DIR /api-response-sample.json"
"$BUNDLE_DIR /summary.txt"
echo
""
echo
"--- DNS & Network ---"
echo
"DNS resolve: $(nslookup api.ideogram.ai 2>/dev/null | grep -A1 'Name:' | tail -1 || echo 'nslookup unavailable') "
echo
"TLS test: $(curl -s -o /dev/null -w '%{ssl_verify_result}' https://api.ideogram.ai/ 2>/dev/null || echo 'failed') "
"$BUNDLE_DIR /summary.txt"
if
env
then
's/=.*/=***REDACTED***/'
env
"$BUNDLE_DIR /env-redacted.txt"
fi
echo
""
echo
"--- Dependencies ---"
echo
"No package.json found"
echo
"No Python ideogram packages"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR .tar.gz"
"$BUNDLE_DIR "
rm
"$BUNDLE_DIR "
echo
"Bundle created: $BUNDLE_DIR .tar.gz"
echo
"Contents: summary.txt, api-response-sample.json, env-redacted.txt"
Step 2: Quick One-Line Diagnostics set -euo pipefail
curl -s -o /dev/null -w "Status: %{http_code} | Time: %{time_total}s\n" \
-X POST https://api.ideogram.ai/generate \
-H "Api-Key: $IDEOGRAM_API_KEY " \
-H "Content-Type: application/json" \
-d '{"image_request":{"prompt":"test","model":"V_2_TURBO","magic_prompt_option":"OFF"}}'
curl -s -o /dev/null -w "V3 Status: %{http_code}\n" \
-X POST https://api.ideogram.ai/v1/ideogram-v3/generate \
-H "Api-Key: $IDEOGRAM_API_KEY " \
-F "prompt=test" -F "rendering_speed=FLASH"
Step 3: Request Logging Wrapper
async function debuggableRequest (url : string , init : RequestInit ) {
const start = Date .now ();
const response = await fetch (url, init);
const elapsed = Date .now () - start;
if (!response.ok ) {
const body = await response.text ();
console .error (JSON .stringify ({
timestamp : new Date ().toISOString (),
url,
method : init.method ,
status : response.status ,
elapsed_ms : elapsed,
error : body.slice (0 , 500 ),
headers : Object .fromEntries (
Object .entries (init.headers ?? {}).map (([k, v] ) =>
[k, k.toLowerCase () === "api-key" ? "***REDACTED***" : v]
)
),
}, null , 2 ));
throw new Error (`Ideogram ${response.status} : ${body} ` );
}
return response;
}
Sensitive Data Handling ALWAYS REDACT before sharing:
API keys and tokens
.env file values
PII in prompts
File paths containing usernames
HTTP status codes and error messages
Request timing and latency
Runtime versions (Node, Python)
Package dependency versions
Error Handling Item Purpose Included API key status Auth verification SET/NOT SET only HTTP status code Error classification Full code Response time Latency diagnosis Seconds DNS resolution Network diagnosis IP only Package versions Compatibility check Version strings
Output
ideogram-debug-YYYYMMDD-HHMMSS.tar.gz containing:
summary.txt -- environment, API test, DNS, dependencies
api-response-sample.json -- truncated API response
env-redacted.txt -- configuration with values masked
Resources
Next Steps For rate limit issues, see ideogram-rate-limits.