incident-response

How this team handles a production incident issue — what to establish before proposing a fix, and what an agent may and may not do on its own.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./examples/plugins/deploy-sentinel/skills/incident-response/SKILL.md

Quality

Content

86%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.

The content is a tight, well-structured incident-response playbook that gives concrete tool guidance, an explicit sequencing order, and sharp do/don't rules without padding. It is strong across the board, with only minor room to formalize call signatures and validation loops.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence throughout — it never explains what an incident or a deploy is, and every line (e.g. 'Get a timestamp before you get a theory') earns its place.	5 / 5
Actionability	It names concrete tool calls (`correlate_deploys`, `request_rollback`) with their arguments and gives copy-ready good/bad 'reason' examples, but full call signatures are not spelled out, leaving minor gaps.	4 / 5
Workflow Clarity	The 'Establish, in this order' sequence is explicit with a clear checkpoint ('Do not skip to step 3') and decision guidance ('An empty result is informative'), but there is no formal validate->fix->retry loop, so it sits just below a 5.	4 / 5
Progressive Disclosure	It is a single well-organized file with clear section headers and no need for external references; content is appropriately self-contained and easy to navigate.	5 / 5
	Total	18 / 20 Passed

Description

53%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.

The description clearly scopes a distinct domain and hints at concrete actions and agent boundaries, but it omits an explicit 'when to use' trigger clause and relies on a single keyword, leaving it solidly mid-tier rather than comprehensive.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user reports a production incident, outage, or SEV and needs to triage before fixing.'

Expand trigger terms with natural synonyms users say (outage, on-call, SEV/page, escalation) to improve recall.

Enumerate the concrete actions more explicitly (establish blast radius/timeline, file rollback requests, update the issue) rather than describing them abstractly.

Dimension	Reasoning	Score
Specificity	Names the incident-response domain and frames concrete actions ('what to establish before proposing a fix', 'what an agent may and may not do on its own'), but the actions are described abstractly rather than enumerated, so it is not comprehensive.	3 / 5
Completeness	It has a clear 'what' (how the team handles an incident, what to establish, agent permissions) but no explicit 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes the natural phrase 'production incident issue', but lacks common synonyms users might say (outage, on-call, SEV, page, escalation), so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	The 'production incident issue' niche is fairly distinct from general debugging skills, with only minor overlap risk; it is mostly distinguishable but lacks the sharp trigger phrasing of a 5.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: multica-ai/multica
Path: examples/plugins/deploy-sentinel/skills/incident-response/SKILL.md
Commit: ea94c7c

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.