gamma-incident-runbook
Manage incident response for Gamma integration issues. Use when experiencing production incidents, outages, or need systematic troubleshooting procedures. Trigger with phrases like "gamma incident", "gamma outage", "gamma down", "gamma emergency", "gamma runbook". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill gamma-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.
# Gamma Incident Runbook ## Overview Systematic procedures for responding to and resolving Gamma integration incidents. ## Prerequisites - Access to monitoring dashboards - Access to application logs - On-call responsibilities defined - Communication channels established ## Incident Severity Levels | Level | Description | Response Time | Escalation | |-------|-------------|---------------|------------| | P1 | Complete outage, no presentations | < 15 min | Immediate | | P2 | Degraded, slow or partial failures | < 30 min | 1 hour | | P3 | Minor issues, workaround available | < 2 hours | 4 hours | | P4 | Cosmetic or non-urgent | < 24 hours | None | ## Quick Diagnostics ### Step 1: Check Gamma Status ```bash set -euo pipefail # Check Gamma status page curl -s https://status.gamma.app/api/v2/status.json | jq '.status' # Check our integration health curl -s https://your-app.com/health/gamma | jq '.' # Quick connectivity test curl -w "\nTime: %{time_total}s\n" \ -H "Authorization: Bearer $GAMMA_API_KEY" \ https://api.gamma.app/v1/ping ``` ### Step 2: Review Key Metrics ```bash set -euo pipefail # Check error rate (Prometheus) curl -s 'http://prometheus:9090/api/v1/query?query=rate(gamma_r
- Overview
- Prerequisites
- Incident Severity Levels
- Quick Diagnostics
- Step 1: Check Gamma Status
- Step 2: Review Key Metrics
- Step 3: Review Recent Logs
- Incident Response Procedures
- Scenario 1: API Returning 5xx Errors
- Scenario 2: Rate Limit Exceeded (429)
- Scenario 3: High Latency
- Scenario 4: Authentication Failures (401/403)
- Communication Templates
- Internal Notification
set -euo pipefail
Check Gamma status page
curl -s https://status.gamma.app/api/v2/status.json | jq '.status'
Check our integration health
curl -s https://your-app.com/health/gamma | jq '.'
Quick connectivity test
curl -w "\nTime: %{time_total}s\n" \
Check error rate (Prometheus)
curl -s 'http://prometheus:9090/api/v1/query?query=rate(gamma_requests_total{status=~"5.."}[5m])' | jq '.data.result' # 9090: Prometheus port
Check latency P95What does the gamma-incident-runbook skill do?
Manage incident response for Gamma integration issues. Use when experiencing production incidents, outages, or need systematic troubleshooting procedures. Trigger with phrases like "gamma incident", "gamma outage", "gamma down", "gamma emergency", "gamma runbook". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill gamma-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,630 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.