ideogram-incident-runbook
Execute Ideogram incident response procedures 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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-incident-runbook91
Does it follow best practices?
Validation for skill structure
Evaluation results
100%
44%Ideogram Integration Outage: Post-Incident Review
Postmortem documentation
Incident header title
0%
100%
Date field present
100%
100%
Duration field present
25%
100%
Severity field present
50%
100%
Summary section
87%
100%
Timeline section with HH:MM format
50%
100%
Root Cause section
70%
100%
Impact section with user count
60%
100%
Impact section with revenue
80%
100%
Action items with checkbox format
0%
100%
Action items have owners and dates
90%
100%
Without context: $0.1936 · 53s · 13 turns · 14 in / 2,532 out tokens
With context: $0.3831 · 1m 22s · 22 turns · 55 in / 3,717 out tokens
93%
34%Stakeholder Communications During Ideogram Outage
Incident communication templates
Slack severity emoji
0%
0%
Slack incident header
20%
100%
Slack Status field
100%
100%
Slack Impact field
100%
100%
Slack Current action field
88%
100%
Slack Next update field
100%
100%
Slack Incident commander field
66%
100%
Status page title
10%
100%
Status page impact description
66%
100%
Status page investigating statement
100%
100%
Status page timestamp
0%
100%
Without context: $0.1127 · 30s · 9 turns · 9 in / 1,384 out tokens
With context: $0.3911 · 1m 8s · 25 turns · 58 in / 3,270 out tokens
100%
23%Ideogram Integration Alert: Investigate and Document Response
Incident triage and remediation plan
Severity classification
100%
100%
Triage step documented
100%
100%
Decision tree applied
100%
100%
Error type identified as 429
100%
100%
Rate limit header check step
100%
100%
RATE_LIMIT_MODE=queue remediation
0%
100%
Long-term action: contact Ideogram
77%
100%
4-step structure
100%
100%
Stakeholder communication mentioned
100%
100%
Evidence collection referenced
55%
100%
kubectl command for remediation
44%
100%
Without context: $0.2655 · 1m 50s · 10 turns · 11 in / 5,486 out tokens
With context: $0.4686 · 1m 55s · 22 turns · 365 in / 6,389 out tokens
- Evaluated
- Agent
- Claude Code
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.