Skip to main content Inicio Creadores jeremylongshore tons-of-skills-marketplace ideogram-debug-bundle
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".
Ir a la instalación Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Mostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill ideogram-debug-bundleEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Más de este repositorio langchain-deploy-integration Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".
langchain-langgraph-agents Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".
langchain-langgraph-human-in-loop Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before /
interrupt_after and Command(resume=...) — JSON-serializable state, clean
resume semantics, and UI wiring for approval decisions. Use when adding an
approval gate before an expensive tool call, wiring a Slack/web UI for agent
approvals, or debugging a graph that crashes on interrupt.
Trigger with "langgraph human in loop", "langgraph interrupt_before",
"langgraph approval flow", "Command resume", "langgraph HITL".
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
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.
