CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable commands and clear incident-response structure, but loses points for missing validation feedback loops on risky operations and for keeping everything monolithic in one file with no reference bundle to offload detail into.

Suggestions

Add explicit validation checkpoints after destructive/batch actions — e.g., after rotating the key or enabling fallback, run the triage curl again and confirm a 200 before declaring mitigated.

Move the communication and postmortem templates (and optionally the TypeScript fallback implementation) into reference files under ./references/ and link to them from SKILL.md to improve progressive disclosure.

Trim inline redundancy — the latency and connectivity curl blocks in triage overlap the Immediate Actions examples — to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient and skips basic concept explanations, but it is fairly long with full triage scripts, a decision tree, fallback code, and templates all inline; it could be tightened by moving templates or code out to references.

2 / 3

Actionability

It provides concrete, executable guidance throughout — copy-paste curl/kubectl bash blocks, a TypeScript fallback function, and step-by-step credit top-up instructions — with specific status codes and commands.

3 / 3

Workflow Clarity

The triage and decision tree sequence is clear, but destructive/batch-style operations (key rotation, kubectl rollout restart, enabling fallback) lack explicit validation checkpoints to confirm the fix worked before proceeding, which caps the score at 2 per the rubric.

2 / 3

Progressive Disclosure

No bundle/reference files exist, so all content lives inline in SKILL.md; while sections are reasonably organized, material like templates and the fallback implementation could be split out, and the only cross-skill pointer ("see ideogram-data-handling") is not a clearly signaled one-level reference into a real bundle file.

2 / 3

Total

9

/

12

Passed

Description

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.

A strong, well-constructed description that explicitly states capabilities, gives natural trigger phrases, and answers both what and when. Third-person voice is maintained throughout, with no fluff or over-claims.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Execute Ideogram incident response with triage, mitigation, and postmortem" — naming specific sub-tasks rather than vague language.

3 / 3

Completeness

It clearly answers both what (incident response with triage, mitigation, postmortem) and when via an explicit "Use when responding to Ideogram-related outages..." clause plus trigger phrases.

3 / 3

Trigger Term Quality

It provides explicit natural trigger phrases a user would actually say: "ideogram incident", "ideogram outage", "ideogram down", "ideogram on-call", "ideogram emergency", "ideogram broken", giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The narrow "Ideogram incident response" niche with Ideogram-specific trigger terms makes it clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.