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".
89
88%
Does it follow best practices?
Impact
—
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 strong skill description that clearly defines its scope (Exa incident response), lists concrete actions (triage, mitigation, postmortem), and provides explicit trigger guidance with natural user phrases. It uses proper third-person voice and is concise without being vague. The description would perform well in a large skill library due to its distinctive Exa-specific triggers.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: triage, mitigation, and postmortem procedures. 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, post-incident reviews) with an explicit 'Use when' clause and a 'Trigger with' clause listing specific 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 'Exa' domain specificity combined with incident response focus. The trigger terms are all prefixed with 'exa' 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 incident response runbook with excellent actionability — executable triage scripts, concrete code for each error scenario, and clear decision trees. The workflow is well-sequenced from triage through post-incident. Minor weaknesses include some content redundancy between the decision tree, immediate actions, and the error handling summary table, and the document could benefit from splitting some detailed sections into bundle files.
Suggestions
Consider removing the 'Error Handling' summary table near the end, as it largely duplicates information already covered in the decision tree and immediate actions sections.
Move the TypeScript code examples (rate limiting, fallback) and communication templates into separate bundle files referenced from the main skill to improve progressive disclosure and reduce the main file length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables and decision trees, but some sections like the communication templates and the error handling table at the end partially duplicate information already covered in the decision tree and immediate actions sections. The overview is lean, but overall there's some redundancy. | 2 / 3 |
Actionability | Excellent actionability throughout — the triage script is copy-paste ready bash, the TypeScript examples for rate limiting and fallback are executable, and every error code has concrete remediation steps with specific commands, URLs, and code snippets. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: severity classification → quick triage script → decision tree → specific actions by error code → communication → post-incident. The triage script serves as an explicit validation checkpoint, and the decision tree provides clear branching logic for error recovery. | 3 / 3 |
Progressive Disclosure | The skill references `exa-data-handling` and `exa-debug-bundle` at the end, and links to external docs, which is good. However, the content is fairly long (~180 lines) and some sections like the TypeScript fallback code and communication templates could potentially be split into referenced files for better organization. Without bundle files, the references to other skills are the only disclosure mechanism. | 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.