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".
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 that clearly defines its scope (Ideogram incident response), lists concrete actions (triage, mitigation, postmortem), provides explicit 'Use when' guidance, and includes a comprehensive set of natural trigger phrases. It uses proper third-person voice throughout and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: triage, mitigation, and postmortem. Also mentions investigating errors and running post-incident reviews, giving a clear picture of what the skill does. | 3 / 3 |
Completeness | Clearly answers both 'what' (execute incident response with triage, mitigation, postmortem) and 'when' (responding to outages, investigating errors, running post-incident reviews) with an explicit 'Use when' clause and trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually 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 combination of 'Ideogram' product scope and 'incident response' domain. The trigger terms are narrowly scoped to Ideogram-specific incidents, making conflicts with other skills very unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable incident runbook with executable triage scripts, a clear decision tree, and specific remediation commands for each failure mode. Its main weakness is length—the postmortem template, communication template, and fallback implementation could be offloaded to separate files to improve token efficiency. The content demonstrates good operational thinking with proper error handling in scripts and logical workflow progression.
Suggestions
Move the postmortem template, communication template, and fallback TypeScript implementation into separate bundle files referenced from the main SKILL.md to improve conciseness and progressive disclosure.
Remove the 'Output' section—it restates what the workflow already makes obvious and adds no actionable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables and code blocks, but includes some sections that could be tightened—the communication templates, postmortem template, and 'Output' section add bulk without much unique value Claude wouldn't already know how to produce. The severity level table is useful but the response time column is operational context Claude can't enforce. | 2 / 3 |
Actionability | Highly actionable with executable bash scripts for triage, specific kubectl commands for remediation, a complete TypeScript fallback implementation, and concrete steps for each error code. Commands are copy-paste ready with proper error handling (set -euo pipefail). | 3 / 3 |
Workflow Clarity | The decision tree provides clear branching logic, the triage script is explicitly sequenced ('Run These First'), and each error code maps to specific remediation steps. The workflow naturally includes validation (run triage → identify error → apply fix → verify), and the fallback implementation includes error recovery logic. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's a long monolithic file (~200 lines) with no bundle files to offload detail. The fallback implementation, communication templates, and postmortem template could reasonably be split into separate referenced files. The single reference to 'ideogram-data-handling' at the end is appropriate but the skill itself could benefit from more decomposition. | 2 / 3 |
Total | 10 / 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 | |
- Commit
3a2d27d
- 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.