deepgram-incident-runbook
Execute Deepgram incident response procedures for production issues. Use when handling Deepgram outages, debugging production failures, or responding to service degradation. "deepgram down", "deepgram emergency", "deepgram 500 errors". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill deepgram-incident-runbook --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Deepgram Incident Runbook ## Overview Standardized incident response for Deepgram-related production issues. Includes automated triage script, severity classification (SEV1-SEV4), immediate mitigation actions, fallback activation, and post-incident review template. ## Quick Reference | Resource | URL | |----------|-----| | Deepgram Status | https://status.deepgram.com | | Deepgram Console | http
What does the deepgram-incident-runbook skill do?
Execute Deepgram incident response procedures for production issues. Use when handling Deepgram outages, debugging production failures, or responding to service degradation. "deepgram down", "deepgram emergency", "deepgram 500 errors". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill deepgram-incident-runbook --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.