CtrlK
BlogDocsLog inGet started
Tessl Logo

incident-response

Manages production incident response workflows from initial triage through postmortem. Guides responders through alert acknowledgment, mitigation, status communication, and follow-up. Use when the user mentions outages, service degradation, on-call pages, incident response, postmortems, error rate spikes, latency issues, or on-call escalation. Covers rollback decisions, stakeholder updates, and structured post-incident review.

72

Quality

87%

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

75%Weight 40%Scale 1-5

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

A well-structured, actionable incident-response workflow with clear sequencing, timebounds, and checklists. The main weakness is vague filler in the Step 4 opener ('do stuff to follow up') and an implicit rather than explicit rollback failure-recovery loop.

Suggestions

Replace the vague Step 4 opener 'do stuff to follow up. Things like writing a postmortem, scheduling a review, etc.' with a direct instruction, since the concrete checklist already follows.

Make the rollback feedback loop explicit, e.g. 'If error rates do not return to baseline after rollback, consider the next most recent change and re-validate before declaring contained.'

Trim redundant sentences like 'Don't worry about root cause yet. Mitigation comes first.' to tighten the token budget.

DimensionReasoningScore

Conciseness

Mostly lean and well-organized with checklists, but padded filler like 'do stuff to follow up. Things like writing a postmortem, scheduling a review, etc.' and 'Don't worry about root cause yet. Mitigation comes first.' could be trimmed.

4 / 5

Actionability

Provides concrete, actionable guidance — timeframes ('within 5 minutes', 'every 15 minutes'), named files (`#inc-<short-name>`, `POSTMORTEM_TEMPLATE.md`), and ready checklists — but the Step 4 intro ('do stuff to follow up') is vague before the concrete checklist rescues it.

4 / 5

Workflow Clarity

Clear four-step sequence (Triage → Mitigate → Communicate → Resolve) with an explicit validation checkpoint ('Confirm error rates and latency return to baseline before declaring the incident contained') and checklists, but the rollback recovery loop is implicit rather than a spelled-out 'if validation fails, do X' branch.

4 / 5

Progressive Disclosure

Well-organized into labeled steps with clearly signaled one-level-deep references to `STATUS_UPDATE_TEMPLATE.md` and `POSTMORTEM_TEMPLATE.md`; minor gap is the inlined postmortem outline and template files that are instructed to be created rather than bundled.

4 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

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' trigger guidance with natural synonyms, and a distinct niche. It cleanly matches the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'alert acknowledgment, mitigation, status communication, and follow-up' plus 'rollback decisions, stakeholder updates, and structured post-incident review' — giving comprehensive coverage of the incident-response domain.

5 / 5

Completeness

Explicitly answers both what ('Manages production incident response workflows from initial triage through postmortem') and when (the 'Use when the user mentions...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

The 'Use when the user mentions outages, service degradation, on-call pages, incident response, postmortems, error rate spikes, latency issues, or on-call escalation' clause covers natural phrases and synonyms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (production incident response) with distinct on-call/outage triggers, making overlap with unrelated skills minimal.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fernandezbaptiste/skill-review-sandbox
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.