ideogram-debug-bundle
Generate a diagnostic bundle of environment and log data for Ideogram support.
Install
mkdir -p .claude/skills/ideogram-debug-bundle && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9202" && unzip -o skill.zip -d .claude/skills/ideogram-debug-bundle && rm skill.zipInstalls to .claude/skills/ideogram-debug-bundle
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Collect Ideogram debug evidence for support tickets and troubleshooting.Key capabilities
- →Generate diagnostic tarball for Ideogram API support
- →Perform API connectivity and latency tests
- →Collect runtime and dependency environment information
- →Verify DNS resolution and TLS connectivity
- →Redact sensitive configuration values from environment files
How it works
The tool executes a series of shell commands to gather system runtime details, network connectivity status, and API response samples. It then packages these diagnostic files into a compressed tarball for support ticket submission.
Inputs & outputs
When to use ideogram-debug-bundle
- →Collecting logs for support tickets
- →Troubleshooting API connectivity issues
- →Auditing current environment configuration
- →Diagnosing generation failures
About this skill
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_KEYenvironment variable setcurlandtaravailable- 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
# --- Environment ---
{
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"
# --- API Connectivity Test ---
{
echo ""
echo "--- API Test (Legacy Generate) ---"
RESPONSE=$(curl -s -w "\nHTTP_STATUS:%{http_code}\nTIME_TOTAL:%{time_total}" \
-X POST https://api.ideogram.ai/generate \
-H "Api-Key: ${IDEOGRAM_API_KEY:-missing}" \
-H "Content-Type: application/json" \
-d '{"image_request":{"prompt":"debug test","model":"V_2_TURBO","magic_prompt_option":"OFF"}}' \
2>&1 || echo "CURL_FAILED")
echo "$RESPONSE" | grep -E "HTTP_STATUS|TIME_TOTAL|error" || true
echo "$RESPONSE" | head -5 > "$BUNDLE_DIR/api-response-sample.json"
} >> "$BUNDLE_DIR/summary.txt"
# --- DNS Resolution ---
{
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"
# --- Local Configuration (redacted) ---
if [ -f .env ]; then
sed 's/=.*/=***REDACTED***/' .env > "$BUNDLE_DIR/env-redacted.txt"
fi
# --- Package versions ---
{
echo ""
echo "--- Dependencies ---"
npm list --depth=0 2>/dev/null || echo "No package.json found"
pip freeze 2>/dev/null | grep -i ideogram || echo "No Python ideogram packages"
} >> "$BUNDLE_DIR/summary.txt"
# --- Package ---
tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR"
rm -rf "$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
# Test API key validity
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"}}'
# Test V3 endpoint
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
// Add to your client for capturing failed requests
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),
// Redact API key from headers
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
.envfile values- PII in prompts
- File paths containing usernames
Safe to include:
- 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.gzcontaining:summary.txt-- environment, API test, DNS, dependenciesapi-response-sample.json-- truncated API responseenv-redacted.txt-- configuration with values masked
Resources
- Ideogram API Overview
- Enterprise support:
[email protected]
Next Steps
For rate limit issues, see ideogram-rate-limits.
When not to use it
- →When rate limit issues are the primary concern
- →When handling PII in prompts without redaction
Prerequisites
Limitations
- →Requires manual redaction of PII in prompts
- →API key status is limited to SET or NOT SET indicators
How it compares
Unlike manual troubleshooting, this tool automates the collection of redacted environment logs and standardized network tests into a single shareable archive.
Compared to similar skills
ideogram-debug-bundle side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ideogram-debug-bundle (this skill) | 0 | 27d | Caution | Intermediate |
| godot | 1,044 | 5mo | Review | Intermediate |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
| error-handling-patterns | 35 | 2mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
error-handling-patterns
wshobson
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
chrome-devtools
mrgoonie
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
unreal-engine-cpp-pro
sickn33
Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.
python-performance-optimization
wshobson
Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.