CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/incident-response-incident-response/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 body presents a well-sequenced multi-phase incident workflow with concrete per-step guidance, but it is undermined by generic boilerplate sections, unexplained template placeholders, and a monolithic single-file structure with no progressive disclosure. Tightening the padding and moving step details into reference files would substantially improve it.

Suggestions

Remove the generic "Use this skill when", "Do not use this skill when", and "Instructions" sections plus the "[Extended thinking: ...]" meta block — they restate the description and add padding without new information.

Explain how the "[user request]" and "P$SEVERITY" placeholders are to be filled (or replace them with a worked example), and add explicit verification loops between phases (e.g., confirm mitigation restored service before moving to root-cause analysis).

Keep SKILL.md as a concise overview (phases, severity levels, coordination protocols) and move the 13 detailed step prompts into per-phase reference files under references/, linked with clear one-level-deep pointers.

DimensionReasoningScore

Conciseness

The 13 step prompts are dense and checklist-like, but the generic "Use this skill when / Do not use this skill when / Instructions" boilerplate, the "[Extended thinking: ...]" meta-commentary block, and the trailing "Production incident requiring immediate response: [user request]" line add unnecessary padding. Not 2: the majority of the body is efficient, actionable material rather than concept explanation.

3 / 5

Actionability

Each step names concrete tools and numbered investigation actions (e.g., "Query: 1) Distributed tracing (OpenTelemetry/Jaeger), 2) Metrics correlation (Prometheus/Grafana/DataDog)"), but there are no executable commands and unresolved placeholders ("[user request]", "P$SEVERITY") with no explanation of how to fill them. Not 4: the placeholder substitution mechanism is a key missing detail that keeps the guidance from being directly executable.

3 / 5

Workflow Clarity

Five clearly sequenced phases with 13 numbered steps, each specifying role, prompt, output, and explicit context handoff to the next step ("Context: Severity level from step 1"), plus validation checkpoints ("Health check validation at each stage", "Rollback triggers configured") and a success-criteria checklist. Not 5: validation between phases is implicit — there is no explicit loop confirming mitigation worked before proceeding to root-cause analysis, and communication oddly follows resolution rather than running in parallel.

4 / 5

Progressive Disclosure

The body has good section structure (phases, severity levels, success criteria), but it is a ~165-line monolithic file with no bundle files — all 13 detailed step prompts, configuration, and coordination protocols are inlined where per-phase reference files would serve better. Not 4: substantial content that should be split out is inline with no references at all; not 2: headers and consistent per-step structure keep it navigable.

3 / 5

Total

13

/

20

Passed

Description

88%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 that clearly and concisely states both the capability set (triage, mitigation, investigation, recovery, follow-up) and explicit trigger conditions in third-person voice. The only weakness is moderate synonym coverage for trigger terms.

DimensionReasoningScore

Specificity

"Coordinate production incident triage, mitigation, investigation, recovery, and follow-up" lists five concrete lifecycle actions with comprehensive coverage of the incident-response domain. Not 4: there are no meaningful gaps in the action coverage from detection through postmortem follow-up.

5 / 5

Completeness

Explicitly answers both questions: "what" ("Coordinate production incident triage, mitigation, investigation, recovery, and follow-up") and "when" ("Use when responding to outages or other incidents that require structured operational coordination"). Matches the anchor-5 example pattern with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use when responding to outages or other incidents" includes the most natural trigger terms (outages, incidents), but misses common variations users would say such as "service down", "downtime", "SEV", or "on-call". Not 5: synonym coverage is good but not comprehensive; not 3 because the key natural phrases are present.

4 / 5

Distinctiveness Conflict Risk

Incident response is a clear niche with distinct triggers (outages, incidents), but "incidents that require structured operational coordination" is broad enough to overlap with security-incident or general ops/SRE coordination skills. Not 5: minor overlap risk with closely related skills remains.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/incident-response-incident-response/SKILL.md

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.