Skills incident-responder
📦

incident-responder

Content revision r2 Safe ⚙️ External commands

Coordinate Reliable Incident Response

Service incidents require fast decisions, clear ownership, and reliable communication. This skill structures triage, investigation, recovery, validation, and post-incident learning.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "incident-responder" from https://skillstore.io/skills/sickn33-incident-responder.md and its manifest at https://skillstore.io/api/skills/sickn33-incident-responder/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-incident-responder.md Signed manifest GET /api/skills/sickn33-incident-responder/manifest Signed lockfile GET /api/skills/sickn33-incident-responder/lockfile

Test it

Using "incident-responder". Checkout errors rose from one percent to forty percent after a payment service deployment.

Expected outcome:

  • Severity: P1 because a major customer journey is degraded.
  • Stabilization: pause the deployment and assess rollback readiness.
  • Validation: monitor checkout success, latency, payment dependency health, and regional impact.
  • Communication: post an initial status update and report progress hourly.

Using "incident-responder". Prepare a post-incident review for a retry storm that exhausted database connections.

Expected outcome:

  • Timeline: capture the triggering failure, retry growth, connection saturation, mitigation, and recovery.
  • Contributing factors: unlimited retries, weak connection alerts, and insufficient capacity protection.
  • Actions: add exponential backoff, retry budgets, connection saturation alerts, and a resilience test.

Security Audit

Safe
v5 • 7/24/2026 Open versioned report

All three static findings are false positives caused by Markdown formatting and ordinary descriptions of SRE incident response. The skill contains guidance only, with no executable commands, system reconnaissance, or prompt injection evidence.

1
Files scanned
215
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (1)
SKILL.md:24
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-incident-responder/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-incident-responder/security.svg)](https://skillstore.io/skills/sickn33-incident-responder?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-incident-responder?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-incident-responder/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-incident-responder.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). incident-responder security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-incident-responder/audits/5

BibTeX citation

@techreport{sickn33-sickn33-incident-responder-2026, author = {sickn33}, title = {incident-responder security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-incident-responder/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "incident-responder security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-24" url: "https://skillstore.io/skills/sickn33-incident-responder/audits/5" identifiers: - type: other value: "skillstore:sickn33-incident-responder:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Lead an Active Outage

Create a prioritized response plan, assign roles, assess impact, and establish update intervals.

Investigate Service Degradation

Correlate recent changes with metrics, traces, logs, dependencies, capacity, and user impact.

Run a Post-Incident Review

Build a blameless timeline, analyze contributing factors, and define measurable prevention and detection improvements.

Try These Prompts

Classify an Incident 
Classify this incident using user impact, business impact, affected systems, and external factors: [incident details]. State assumptions and missing information.
Create a Response Plan 
Build a first-30-minute response plan for [incident]. Assign roles, prioritize stabilization, define validation checks, and draft internal and customer updates.
Guide an Observability Investigation 
Analyze these symptoms and telemetry: [details]. Propose ranked hypotheses and checks across changes, metrics, traces, logs, dependencies, capacity, databases, and networks.
Design Recovery and Follow-Up 
Using this incident timeline and evidence: [details], propose a staged recovery plan, rollback criteria, validation gates, contributing factors, and measurable follow-up actions.

Best Practices

  • Prioritize service restoration while preserving evidence and rollback options.
  • Use current telemetry to test ranked hypotheses and record every important decision.
  • Communicate on a fixed schedule with detail appropriate for each audience.

Avoid

  • Do not make high-risk production changes without ownership, validation, and rollback criteria.
  • Do not delay stakeholder updates until the root cause is known.
  • Do not treat a temporary symptom reduction as confirmed recovery.

Frequently Asked Questions

Can this skill operate monitoring or deployment tools?
No. It provides structured guidance based on information supplied by the user.
Which incidents does this skill support?
It supports service outages, degraded performance, dependency failures, capacity problems, and related reliability events.
Does it replace an organizational incident runbook?
No. Local runbooks, escalation policies, compliance requirements, and authority boundaries remain controlling.
Can it help classify severity?
Yes. It considers user impact, business impact, system scope, and external factors.
Can it prepare customer communications?
Yes. It can draft clear status updates, but authorized staff must review and publish them.
Can it support post-incident work?
Yes. It can structure timelines, contributing factors, root cause analysis, action items, and follow-up measures.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/incident-responder

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

9 downloads · 108 views

File structure

📄 SKILL.md

More from sickn33

View all

Related Skills

View all