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".
Jump to install Skills Marketplace Discover and explore AI skills built by the community.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Show prompt details A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-debug-bundleThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Download Zip Downloading... More from this 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".
Related occupations SOC
Based on SOC occupation classification
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 setcurl and tar availablePermission 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} "
} >> "$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 valuesPII 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, dependenciesapi-response-sample.json -- truncated API responseenv-redacted.txt -- configuration with values masked
Resources
Next Steps For rate limit issues, see ideogram-rate-limits.
