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
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description with strong completeness and excellent trigger term coverage. The explicit 'Use when' clause and enumerated trigger phrases make it highly actionable for skill selection. The main weakness is that the capability actions (triage, mitigation, postmortem) are somewhat generic incident response terminology rather than Ideogram-specific procedures.
Suggestions
Consider adding more specific Ideogram-related actions beyond generic incident response terms (e.g., 'check Ideogram API status', 'review image generation queue', 'verify API key validity')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Ideogram incident response) and lists some actions (triage, mitigation, postmortem), but these are somewhat generic incident response terms rather than highly specific concrete actions unique to Ideogram. | 2 / 3 |
Completeness | Clearly answers both what (execute incident response procedures with triage, mitigation, postmortem) and when (responding to outages, investigating errors, running post-incident reviews) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'ideogram incident', 'ideogram outage', 'ideogram down', 'ideogram on-call', 'ideogram emergency', 'ideogram broken' - these are realistic phrases someone would use during an incident. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific 'Ideogram' qualifier throughout - unlikely to conflict with generic incident response skills or other integration-specific skills. The trigger terms are all Ideogram-prefixed. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality incident runbook that provides concrete, actionable guidance for Ideogram incident response. The decision tree, executable commands, and communication templates are excellent. The only weakness is that the document could benefit from splitting some detailed procedures into separate reference files to improve progressive disclosure.
Suggestions
Consider moving detailed remediation procedures (401/403, 429, 500/503 sections) to a separate REMEDIATION.md file, keeping only quick references in the main runbook
The postmortem template could be extracted to a separate POSTMORTEM_TEMPLATE.md file with a brief reference in the main document
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and code blocks to convey information densely. No unnecessary explanations of concepts Claude would already know; every section serves a clear purpose in incident response. | 3 / 3 |
Actionability | Provides fully executable bash commands, specific kubectl operations, and copy-paste ready templates. The triage commands, remediation steps, and communication templates are all immediately actionable. | 3 / 3 |
Workflow Clarity | Clear decision tree for triage, explicit numbered steps in the Instructions section, and well-defined severity levels with response times. The workflow includes validation checkpoints (check status → identify source → remediate → communicate → collect evidence). | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is somewhat long and could benefit from splitting detailed remediation procedures into separate files. The reference to 'ideogram-data-handling' at the end shows awareness of progressive disclosure but most content is inline. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Reviewed
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.