Communitygithub.com

SEV-Triage

Klassifiziert die Schweregrad (SEV1-4) von Vorfällen anhand von Auswirkungs-, Umfangs- und Dringlichkeitssignalen und entscheidet, wen es zu pagen gilt.

Was ist SEV-Triage?

Diese Fähigkeit unterstützt einen KI-Agenten oder ein Tool wie Claude Code, Cursor oder Codex bei der schnellen und systematischen Schweregradklassifizierung von Vorfällen (SEV1-4). Sie ersetzt emotionale Entscheidungen durch eine strukturierte Checkliste: Auswirkungssignale (z. B. Zahlungs- oder Datenintegritätsfluss) werden priorisiert, der Blastradius sowie die Wachstumsrate bewertet und darauf basierend die Eskalationsstufe festgelegt. Die Fähigkeit definiert klare Paging-Regeln, legt eine erneute Triage nach 30 Minuten fest und produziert einen standardisierten Triage-Bericht. Sie ist plattformunabhängig und kann in Incidents-Management-Workflows integriert werden, um Reaktionszeiten zu verbessern und menschliches Zögern zu vermeiden.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/SkillMedev/skills/tree/HEAD/skills/sev-triage
Original anzeigen→Alle Skills durchsuchen

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Dokumentation

Was macht SEV-Triage?

Schweregrad ist eine Entscheidung zum Paging, kein Gradmesser für Gefühle. Weise den höchsten SEV zu, den ein einzelnes Signal rechtfertigt, und stuft nur mit Belegen zurück.

Schweregraddefinitionen

  • SEV1 – Umsatzbeeinträchtigend oder vollständiger Serviceausfall. Mehr als 5 % der Nutzer können einen kritischen Fluss nicht abschließen. Datenverlust oder -verletzung möglich. Page sofort IC, Engineering Lead und Exec-On-Call.
  • SEV2 – Signifikante Beeinträchtigung. Kernfunktion für eine Teilmenge defekt, erhöhte Fehlerrate über SLO-Schwellwert, oder es existiert eine Umgehungslösung, die langfristig inakzeptabel ist. Page IC und Team-On-Call innerhalb von 5 Minuten.
  • SEV3 – Teilweise oder geringfügige Beeinträchtigung. Nicht-kritische Funktion betroffen, SLO noch im Budget, noch keine Eskalation durch Kunden. Ticket erstellt, Team asynchron benachrichtigt, Behebung bis zum nächsten Arbeitstag.
  • SEV4 – Kosmetisch oder Grenzfall. Keine Nutzerauswirkung, proaktiv erkannt. Nur Ticket.

Signal-Checkliste

Beantworte diese Fragen, um auf einen SEV zu kommen. Das erste ‚Ja‘, das zutrifft, gewinnt.

  1. Ist ein Zahlungs-, Authentifizierungs- oder Datenintegritätsfluss für einen beliebigen Nutzer unterbrochen? → SEV1-Kandidat.
  2. Liegt die Fehlerrate in den letzten 10 Minuten über deinem SLO-Schwellwert? → Mindestens SEV2.
  3. Sind mehrere Regionen oder Verfügbarkeitszonen betroffen? → Um eine Stufe hochstufen.
  4. Besteht aktives Risiko von Datenschutzverletzung oder -korruption? → SEV1 unabhängig von der Nutzeranzahl.
  5. Ist ein einzelner nicht-kritischer Endpunkt langsam, aber der Rest gesund? → SEV3.

Umfangsmultiplikatoren

  • Blastradius: Schätze den Prozentsatz der betroffenen Nutzer. Unter 1 % rechtfertigt selten SEV1, es sei denn, die 1 % sind zahlende Kunden oder das Datenrisiko ist schwerwiegend.
  • Wachstumsrate: Breitet sich die Auswirkung aus? Ein SEV3, der sich alle 10 Minuten verdoppelt, ist ein SEV2.
  • Erkennungsverzögerung: Wenn das Problem bereits mehr als 30 Minuten unentdeckt begonnen hat, nimm an, dass der Blastradius größer ist als die derzeitigen Signale zeigen.

Wen zu pagen

  • SEV1: IC (Incident Commander), Service Owner, On-Call SRE und Engineering Lead. Sofort einen War Room eröffnen.
  • SEV2: IC und Service Owner On-Call. Andere nach Bedarf einladen.
  • SEV3: Service-Team On-Call asynchron. Kein War Room.
  • SEV4: Ticket, kein Page.

Durchgearbeitetes Beispiel: Die Entscheidung

Schlecht: „Der Checkout scheint für einige Nutzer defekt zu sein. Fühlt sich wie ein SEV3 an – ich untersuche zuerst die Ursache und benachrichtige jemanden, wenn es ernst wird.“

Gut: „Checkout-Fehlerrate bei 12 % in den letzten 15 Minuten (SLO-Schwellwert: 1 %). Zahlungsfluss unterbrochen → Signal 1 → SEV1. IC, Service Owner und On-Call SRE um 14:32 Uhr gepaged; War Room eröffnet. Blastradius-Schätzung: ~12 % der Checkout-Versuche, Wachstum unklar. Ursache unbekannt – irrelevant für den SEV. Erneute Triage um 15:00 Uhr.“

Die schlechte Version dreht die Reihenfolge um (Ursache vor Schweregrad), zögert bei einem defekten Zahlungsfluss und verzögert das Paging. Die gute Version zitiert das Signal, das die Stufe festlegt, paget sofort, erfasst den Blastradius und plant die erneute Triage – alles bevor jemand weiß, warum es kaputtging.

Liefergegenstand

Erstelle einen Triage-Bericht – gepostet im Incident-Kanal oder Ticket – mit: zugewiesenem SEV, einer einzeiligen Begründung mit dem Namen des Checklisten-Signals, das ihn festlegte, der Blastradius-Schätzung (Prozentsatz der Nutzer oder Anfragen), wer wann gepaged wurde, und der geplanten erneuten Triage-Zeit. Der Bericht ermöglicht es dem nächsten Responder, der Stufe zu vertrauen, anstatt sie neu abzuleiten.

Qualitätsbarriere

  • Der SEV wurde anhand von Auswirkungssignalen zugewiesen, bevor eine Ursachenuntersuchung begann.
  • Die Begründung nennt ein spezifisches Signal aus der Checkliste, kein Bauchgefühl.
  • Das Paging erfolgte bei der Zuweisung, nicht nach Bestätigung – ein potenzieller SEV1 wird auf einen einzigen Datenpunkt hin gepaged.
  • Eine erneute Triage-Zeit ist festgelegt (alle 30 Minuten), und die Stufe bewegt sich mit den Beweisen nach oben und unten.

Dos and Don'ts

  • Do: Weise den SEV zu, bevor du die Ursache untersuchst. Schweregrad betrifft die aktuelle Auswirkung, nicht die Ursache.
  • Do: Führe alle 30 Minuten eine erneute Triage durch. Ein gelöster SEV2 ist ein SEV4; ein sich ausbreitender SEV3 ist ein SEV1.
  • Don't: Stufe niedriger ein, um Leute nicht zu wecken. Falsche SEV1 sind günstiger als übersehene.
  • Don't: Warte auf einen zweiten Datenpunkt, bevor du bei einem potenziellen SEV1 pagest.

Individual skills in this repo

This repo contains 19 individual skills — each has its own dedicated page.

SkillMedev/skills

Designs REST API surfaces - resource naming, HTTP method and status-code semantics, error shapes, pagination, and filtering - and delivers an endpoint spec a consumer can build against without asking questions. Use when someone asks "how should I name this endpoint", "what status code should this return", "should this be PUT or PATCH", "how do I paginate this list", or is reviewing an API before it ships to external consumers. Do NOT use for planning breaking-change rollouts and deprecation windows - use api-versioning-strategist instead; for GraphQL type and resolver design - use graphql-schema instead; for generating client SDKs from an existing spec - use api-client-generator instead; for designing inbound webhook endpoints - use webhook-receiver-hardener instead.

SkillMedev/skills

Produce an accurate, properly timed caption track (SRT or WebVTT) from a video's audio - transcribing or aligning to the voiceover script, timing cues to speech, and enforcing line-length and reading-speed rules so captions are readable and in sync. Use when someone says "generate captions", "make subtitles from the audio", "transcribe and caption this", "export an SRT or VTT", "the captions are out of sync", or "the subtitles flash by too fast to read". Do NOT use to burn-in, style, reframe, or position an existing caption track for a platform (9:16, brand styling, safe areas) - that is social-video-formatter; do NOT use to animate text word-by-word as a motion graphic - that is kinetic-typography; do NOT use to write the spoken script in the first place - that is narration-script.

SkillMedev/skills

Turns data and charts into a decision-driving narrative structured as headline finding, trend, implication, and recommended action - with finding-led chart titles, context for every number, annotation guidance, and honest flags on any conclusion the data cannot support. Use when someone says "turn these numbers into a story", "what's the takeaway from this data", "help me present these results to leadership", or has charts but no narrative. Do NOT use for compressing a long document into a one-pager - use executive-summary instead - or for running the analysis that produces the findings - use eda-playbook instead.

SkillMedev/skills

Use when a task needs live or historical money data - "convert USD to EUR", "current/past exchange rate", "FX rate on this date / over this range", or "current price of Bitcoin/Ethereum, market cap, 24h change". Frankfurter (ECB reference rates, no key) is the FX default; CoinGecko's free keyless tier covers crypto. Do NOT use for stock quotes or equities - no keyless stock API survives verification, say so instead of guessing; do NOT use for country economic indicators like GDP or inflation series - use government-open-data instead; if the request is a vague "I need live data", route through public-data-api-picker.

SkillMedev/skills

Builds a driver-based FP&A operating model linking business inputs to P&L, balance sheet, and cash flow outputs. Use when building an annual plan, preparing investor materials, running scenario analysis, or stress-testing the business.

SkillMedev/skills

Use when a task needs live geographic lookups - "geocode this address", "what's at these coordinates" (reverse geocoding), "lat/lon for this city", "which country/state is this ZIP or postal code in", or "country facts: capital, currency, population, flag". Nominatim (OpenStreetMap) is the geocoding default; Zippopotam for postal codes; APICountries for country facts. All keyless. Do NOT use for weather at a location - use weather-climate instead; do NOT use for country-level statistics over time (GDP, population trends) - use government-open-data instead; if the request is a vague "I need live data", route through public-data-api-picker.

SkillMedev/skills

Runs the full Getting Things Done loop - capture, clarify, organize, reflect, engage - building a trusted system of context lists, a projects list with defined next actions, and a weekly review habit. Use when someone says "I'm overwhelmed and things are slipping through the cracks", "set up GTD for me", "help me do a brain dump and organize it", or "my to-do list is a mess". Do NOT use for just running the weekly review ritual itself - use weekly-review instead - or for clearing an email backlog - use inbox-zero.

SkillMedev/skills

Processes any email backlog to zero using the 4Ds - Delete, Delegate, Defer, Do - with a mass-archive strategy for the obvious, a touch-each-email-once discipline, and a keep-it-clear system of batched processing windows, ruthless unsubscribing, filters, and a minimal folder setup. Use when someone says "I have 5,000 unread emails", "help me get to inbox zero", "email is eating my whole day", or treats their inbox as a to-do list. Do NOT use for drafting the reply emails themselves or prioritization rules for an ongoing support queue - use email-triage instead - or for protecting focus time around the email windows - use deep-work-planner instead.

SkillMedev/skills

Write landing-page copy section by section - hero, social proof, features-as-benefits, objections, CTA - leading with one promise and proving it down the page. Use when someone asks "write my landing page", "improve my hero headline", "what should the homepage say", "turn these features into benefits", or is shipping a new page for a launch or campaign. Do NOT use for testing and optimizing an existing page's conversion rate - use landing-page-cro instead; for the one-line claim itself use positioning-statement; for the full message ladder use messaging-hierarchy.

SkillMedev/skills

Improves an existing landing page's conversion rate through evidence-first CRO - audit heatmaps and recordings, write structured hypotheses, prioritize with ICE scoring, and run one-variable tests to statistical significance. Use when someone asks "why isn't my landing page converting", "audit this page before we scale spend", "which A/B test should we run first", or after a CVR drop or ahead of a paid-traffic push. Do NOT use for writing a new landing page from scratch - use landing-page-copy instead. Do NOT use for auditing the ad accounts sending the traffic - use paid-acquisition-audit instead. Do NOT use for reading the results of a finished experiment - use ab-test-analyzer instead.

SkillMedev/skills

Runs structured coaching sessions using values clarification and the GROW model, ending every session with one committed action, a deadline, and an if-then plan for the likely obstacle. Use when someone says "I feel stuck in my life", "help me figure out what I want", "hold me accountable to my goals", or "coach me through this decision". Do NOT use for building a stress toolkit - use stress-management instead - or a journaling practice - use journal-framework; for a standing goal-tracking system, use goals-accountability. Coaching, not therapy: signs of clinical distress route to a licensed professional.

SkillMedev/skills

Adapts English content for a target language and region - swapping idioms, setting the right formality register, replacing cultural references, converting dates, units, and currency - and delivers the localized text with a notes column explaining each adaptation and flagging what needs a native reviewer. Use when someone asks "localize this copy for the Japanese market", "adapt our marketing copy for the Mexican market", "make this translation sound native instead of literal", or a literal translation reads foreign, stiff, or risky. Do NOT use for auditing in-product UI text quality - use ux-writing-audit instead.

SkillMedev/skills

Turns a natural-language video brief into a complete, ready-to-preview Remotion composition - extracts duration, scenes, brand colors, aspect ratio, and real copy; plans the frame budget; and writes data-driven React/TypeScript using useCurrentFrame, interpolate, spring, AbsoluteFill, and Sequence, registered in Root.tsx. Use when someone says "build a 20-second product demo video", "animate a feature walkthrough", "write the Remotion code for this marketing clip", or wants a scene-by-scene composition they can scrub in Studio. Do NOT use for rendering, iterating, or batching the finished MP4 - use remotion-render instead - or for installing and scaffolding the project - use remotion-setup instead.

SkillMedev/skills

Scaffolds a new Remotion video project wired for Claude Code Agent Skills - Node check, create-video scaffold, skills install, folder conventions, Google Fonts, and a smoke-test render. Use whenever someone wants to start making videos with Remotion and Claude, even just "make product videos with Claude.

SkillMedev/skills

Use the Skill Me catalog from inside any conversation - discover, install, and manage Claude skills through the Skill Me MCP, and load installed skills automatically each session.

SkillMedev/skills

Write one platform-native caption from a topic and brand voice, with a front-loaded hook, native length, and a single earned CTA. Use when the user gives a topic (and optionally brand voice or a described image/video) and asks for an Instagram, LinkedIn, X/Twitter, or TikTok caption. Do NOT use when the user wants a dedicated standalone LinkedIn post - use linkedin-post-writer instead; or a multi-post X thread - use tweet-thread-builder instead; or to adapt one existing piece of content into versions for several channels - use cross-platform-reformatter instead.

SkillMedev/skills

Reframe and export a finished video for social platforms - 9:16 ↔ 16:9 cropping, burned-in captions, a platform-native first frame, loop design, and per-platform specs (aspect, length, safe areas) for TikTok, Reels, Shorts, X, and LinkedIn. Use when someone says "make this vertical", "crop to 9:16", "format for TikTok/Reels/Shorts", "add captions/subtitles", "why is my video cut off on mobile", "resize for Instagram", or "export for social". Do NOT use when the question is about the storyboard or shot order before any video exists (use video-storyboard); the animation craft of how elements move (use motion-design-principles); animated word-by-word caption styling (use kinetic-typography); palette, contrast, or lighting (use motion-color-and-light); directing the product-demo content and screen choreography (use product-demo-director); or scoring, beat-syncing, or audio (use sound-and-music-sync) - this is the craft layer that decides WHAT to format for the feed, then hands a concrete spec to remotion-compo...

SkillMedev/skills

Writes and tunes PySpark jobs - join strategy and broadcast size limits, shuffle-partition sizing, skew diagnosis and salting, UDF avoidance, caching, and output file layout - with concrete size and skew thresholds. Use when someone asks "why is my Spark job slow", "should I broadcast this join", "one task takes forever while the rest finish", "my job OOMs during a join", or is writing a new PySpark ETL job. Do NOT use for Kafka topic, consumer-group, or streaming-pipeline design - use kafka-pipelines instead; do NOT use for single-machine dataframe work that fits in memory - use pandas-expert instead.

SkillMedev/skills

Builds clean, performant, accessible SwiftUI views with correct state ownership, scoped invalidation, and smooth list scrolling, and reviews existing SwiftUI code against a concrete frame-time and re-render budget. Use when someone asks "why does my SwiftUI list stutter", "should this be @State or @Observable", "my whole screen re-renders when one row changes", "how do I animate this transition", or wants a SwiftUI view built or refactored. Do NOT use for cross-platform React Native apps - use react-native-pro instead; do NOT use for Flutter widget trees - use flutter-widget-architect instead; do NOT use for Android Compose UIs - use jetpack-compose-builder instead.

Verwandte Skills

steipete/video-frames

Extract frames or short clips from videos using ffmpeg.

community

steipete/summarize

Summarize or transcribe URLs, YouTube/videos, podcasts, articles, transcripts, PDFs, and local files.

community

openclaw/openclaw

Use when testing, fixing, or extending the OpenClaw Control UI GUI with Vitest + Playwright end-to-end checks, mocked Gateway WebSocket flows, mocked dashboard runs, screenshots/videos, or agent-verifiable browser proof.

community

obra/superpowers

Obra superpowers agent skills.

community

affaan-m/ECC

See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio...

community

affaan-m/everything-claude-code

End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches. Use when planning or executing a multi-channel product launch, or producing landing page, email, social, or ad copy.

community