Agent skill

ideogram-incident-runbook

Execute Ideogram incident response with triage, mitigation, and postmortem. Use when responding to Ideogram-related outages, investigating errors, or running post-incident reviews for Ideogram integration failures. Trigger with phrases like "ideogram incident", "ideogram outage", "ideogram down", "ideogram on-call", "ideogram emergency", "ideogram broken". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-coderead-onlyMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-incident-runbook --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.10.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadGrepBash(kubectl:*)Bash(curl:*)
Requires: Designed for Claude Code, also compatible with Codex and OpenClaw
Path: skills/.curated/ideogram-incident-runbook/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Ideogram Incident Runbook ## Overview Rapid incident response for Ideogram API outages, auth failures, rate limiting, and degraded generation quality. Covers triage, immediate remediation, fallback activation, and postmortem process. ## Severity Levels | Level | Definition | Response Time | Example | |-------|------------|---------------|---------| | P1 | API unreachable or all requests failing | < 15 min | 401 on valid key, 500 on all requests | | P2 | Degraded quality or performance | < 1 hour | P95 latency > 30s, high 429 rate | | P3 | Minor impact, workaround exists | < 4 hours | Occasional safety rejections, slow downloads | | P4 | No user impact | Next business day | Monitoring gaps, stale cache | ## Quick Triage (Run These First) ```bash set -euo pipefail echo "=== IDEOGRAM TRIAGE ===" # 1. Test API connectivity and auth echo -n "API status: " curl -s -o /dev/null -w "%{http_code}" \ -X POST https://api.ideogram.ai/generate \ -H "Api-Key: $IDEOGRAM_API_KEY" \ -H "Content-Type: application/json" \ -d '{"image_request":{"prompt":"triage test","model":"V_2_TURBO","magic_prompt_option":"OFF"}}' echo "" # 2. Test V3 endpoint echo -n "V3 status: " curl -s -o /dev/null -w "%{http

What's inside
Steps it walks through
  1. Overview
  2. Severity Levels
  3. Quick Triage (Run These First)
  4. Decision Tree
  5. Immediate Actions
  6. 401 -- Authentication Failure
  7. 429 -- Sustained Rate Limiting
  8. 500/503 -- Ideogram Outage
  9. 402 -- Credits Exhausted
  10. Fallback Implementation
  11. Communication Templates
  12. Internal (Slack)
  13. Postmortem Template
  14. Error Handling
Commands it runs
set -euo pipefail
echo "=== IDEOGRAM TRIAGE ==="
echo -n "API status: "
curl -s -o /dev/null -w "%{http_code}" \
echo ""
echo -n "V3 status: "
echo -n "DNS: "
nslookup api.ideogram.ai 2>/dev/null | grep -A1 "Name:" | tail -1 || echo "lookup failed"
echo -n "Latency: "
curl -s -o /dev/null -w "%{time_total}s" \
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the ideogram-incident-runbook skill do?

Execute Ideogram incident response with triage, mitigation, and postmortem. Use when responding to Ideogram-related outages, investigating errors, or running post-incident reviews for Ideogram integration failures. Trigger with phrases like "ideogram incident", "ideogram outage", "ideogram down", "ideogram on-call", "ideogram emergency", "ideogram broken". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-incident-runbook --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going