incident-responder

Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management. Masters incident command, blameless post-mortems, error budget management, and system reliability patterns. Handles critical outages, communication strategies, and continuous improvement. Use IMMEDIATELY for production incidents or SRE practices.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/incident-responder/SKILL.md

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.

A well-sequenced incident-response playbook with clear phases and useful severity/SLA specifics, but it is a monolithic wall of abstract checklists padded with boilerplate and redundant sections. It lacks executable commands/templates and would benefit from splitting reference material into separate files.

Suggestions

Remove the generic 'Use this skill when'/'Do not use'/'Instructions' boilerplate and the redundant Purpose section; let the frontmatter description carry that load.

Add concrete, copy-paste-ready artifacts: status-page update templates, incident-channel naming conventions, and example commands for common observability tools.

Split the severity classification, tools/integrations, and SRE best-practices sections into referenced files (e.g., SEVERITY.md, TOOLS.md) and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly list-based rather than prose, but the generic boilerplate header ('Use this skill when', 'Instructions') and redundant Purpose/Behavioral Traits/Response Principles sections restate the description and could be trimmed.	3 / 5
Actionability	Provides checklists and some concrete numbers (SLA thresholds, 'every 15 minutes'), but guidance is largely abstract tool name-drops with no commands, templates, or executable steps.	3 / 5
Workflow Clarity	Presents a clear phased sequence (First 5 minutes -> Investigation -> Resolution -> Post-Incident) with a Recovery Validation checkpoint, though error-recovery feedback loops are only implicit.	4 / 5
Progressive Disclosure	A single monolithic document with no bundle files; severity tables, tool lists, and best-practice sections are inlined that could be split into clearly-signaled one-level-deep references.	3 / 5
	Total	13 / 20 Passed

Description

75%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 solid third-person description that states concrete capabilities and includes an explicit use-trigger, distinguishing it as an SRE incident-response skill. It loses points mainly for a trigger list that could be broader and more scenario-specific.

Suggestions

Expand the 'Use when' clause with concrete triggers users actually say: 'production outage', 'on-call escalation', 'SEV-1/P0', 'pager alert', 'post-mortem'.

Trim the abstract capability list ('Masters...', 'Handles...') in favor of a tighter enumeration of the specific actions the skill performs.

Add file/term synonyms (e.g., 'incident report', 'blameless retro') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the SRE incident-response domain and lists several concrete capabilities (incident command, blameless post-mortems, error budget management, critical outages), though coverage is broad rather than tightly enumerated.	4 / 5
Completeness	Clearly states what the skill does and provides an explicit 'Use IMMEDIATELY for production incidents or SRE practices' trigger, but the when-clause could enumerate more specific scenarios.	4 / 5
Trigger Term Quality	Includes natural triggers like 'production incidents', 'SRE practices', and 'critical outages', but omits common synonyms users would say such as on-call, outage, SEV, or pager.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear SRE incident-response niche with distinct triggers, with only minor overlap risk against general devops or observability skills.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/incident-responder/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.