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?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-3

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

A highly actionable, well-sequenced incident runbook with executable code throughout and no unnecessary concept explanation. The main weakness is progressive disclosure: content is monolithic and the only references point to sibling skills rather than real bundle files.

Suggestions

Split the communication templates and postmortem template into a references/ file (e.g. references/templates.md) linked from the body, so the main SKILL.md stays a concise overview.

Add an explicit "verify mitigation" checkpoint (e.g. re-run the triage script to confirm recovery) to close the incident-response feedback loop.

Confirm the referenced exa-data-handling and exa-debug-bundle skills exist, or relabel them as companion skills rather than implicit bundle references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, providing Exa-specific facts (requestId, 10 QPS, error codes) Claude would not already know with no padding about general API concepts.

3 / 3

Actionability

It supplies fully executable bash triage/evidence scripts, TypeScript caching and fallback code, and curl/kubectl commands that are copy-paste ready.

3 / 3

Workflow Clarity

A clear sequence (Quick Triage → Decision Tree → Immediate Actions → Communication → Post-Incident) with the triage script acting as a verification probe and the decision tree providing error-recovery branching.

3 / 3

Progressive Disclosure

Sections are well-organized, but the ~150-line body is monolithic with no split to bundle files, and the "Next Steps" references point to other skills (exa-data-handling, exa-debug-bundle) rather than actual bundled references in this skill.

2 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 description: third-person voice, concrete actions, explicit use-when clause, and a rich set of natural trigger phrases scoped to a clear niche. No significant weaknesses to address.

DimensionReasoningScore

Specificity

"Execute Exa incident response with triage, mitigation, and postmortem procedures" lists multiple concrete, distinct actions rather than vague language.

3 / 3

Completeness

It states both what it does (triage/mitigation/postmortem) and when to use it ("Use when responding to Exa-related outages...") with explicit trigger guidance.

3 / 3

Trigger Term Quality

Trigger phrases "exa incident", "exa outage", "exa down", "exa on-call", "exa emergency", "exa broken" are natural terms a user would actually say during an incident.

3 / 3

Distinctiveness Conflict Risk

The Exa search API incident niche with dedicated triggers is 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.