AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Sev1 First 15 Minutes

skill-bregman-arie-devops-sre-skills-sev1-first-15-minutes · by bregman-arie

Execute the initial incident workflow to stabilize, communicate, and delegate.

No reviews yet
0 installs
25 views
0.0% view→install

Install

$ agentstack add skill-bregman-arie-devops-sre-skills-sev1-first-15-minutes

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-bregman-arie-devops-sre-skills-sev1-first-15-minutes)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
6mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Sev1 First 15 Minutes? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

When to use

Use for a confirmed high-severity production incident.

Preconditions

  • You have an incident channel and a path to page additional responders.

Procedure

  1. Declare severity and open an incident channel.
  2. Assign roles: incident commander, comms lead, operations lead.
  3. State the customer impact in one sentence.
  4. Stabilize first: stop the bleeding (rollback, disable feature, shed load).
  5. Start a timeline and capture key actions/decisions.

Decision points

  • If impact is unknown: prioritize measurement and narrowing scope.
  • If rollback is low-risk and likely effective: rollback early.
  • If data integrity is at risk: freeze writes and escalate.

Verification

  • Leading indicators improve (error rate, latency, saturation).
  • Customer reports decrease.
  • Comms cadence is established.

Rollback / undo

  • If mitigation worsens impact, revert and try the next lowest-risk action.

Escalation

  • Escalate to security if incident involves auth, data exposure, or suspicious activity.
  • Escalate to leadership if SLA/SLO breach is likely.

Examples

Initial update template:

Impact: 
Start: 
Current status: 
Mitigation in progress: 
Next update: 

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.