CtrlK
BlogDocsLog inGet started
Tessl Logo

exa-incident-runbook

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

76

Quality

96%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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 is concise, actionable, and well-structured. It provides executable triage scripts, clear decision trees, concrete remediation code, and useful communication templates without wasting tokens on explanations Claude already knows. The only minor weakness is that the content is somewhat long for a single file and could benefit from splitting detailed code examples into referenced bundle files.

DimensionReasoningScore

Conciseness

The content is lean and efficient throughout. It avoids explaining what APIs, HTTP codes, or incident response are. Every section delivers actionable information without padding. The tables, decision tree, and code blocks are all dense with useful content.

3 / 3

Actionability

Provides fully executable bash scripts for triage, concrete TypeScript code for rate limiting and fallback patterns, copy-paste ready communication templates, and specific URLs for remediation (dashboard.exa.ai). The decision tree maps errors directly to actions.

3 / 3

Workflow Clarity

The workflow is clearly sequenced: severity classification → quick triage script → decision tree → specific remediation by error code → communication → post-incident review. The triage script has built-in validation (checking HTTP code, showing error details). The decision tree provides clear branching logic for error recovery.

3 / 3

Progressive Disclosure

The content is well-structured with clear sections and headers, and references `exa-data-handling` and `exa-debug-bundle` at the end. However, some sections (like the TypeScript code examples and communication templates) could potentially be split into referenced files to keep the main runbook more scannable. The external references at the bottom are minimal and not deeply signaled.

2 / 3

Total

11

/

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.

This is a strong skill description that clearly defines its scope (Exa incident response), lists concrete actions (triage, mitigation, postmortem), provides explicit 'Use when' guidance, and includes natural trigger phrases. It uses proper third-person voice and is concise without being vague. The only minor improvement would be mentioning specific technical artifacts or tools involved in the process.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: triage, mitigation, and postmortem procedures. These are distinct, well-defined incident response activities.

3 / 3

Completeness

Clearly answers both 'what' (triage, mitigation, postmortem procedures for Exa incidents) and 'when' (explicit 'Use when' clause covering outages, error investigation, and post-incident reviews, plus explicit trigger phrases).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would actually say: 'exa incident', 'exa outage', 'exa down', 'exa on-call', 'exa emergency', 'exa broken'. These are realistic phrases someone would use during an incident.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive due to the specific 'Exa' domain qualifier combined with incident response focus. The trigger terms are all prefixed with 'exa', making conflicts with generic incident response or other integration skills very unlikely.

3 / 3

Total

12

/

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.

Validation9 / 11 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

9

/

11

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.