New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Gamma Incident Runbook

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Manage incident response for Gamma integration issues. An agent skill from jeremylongshore/tons-of-skills-marketplace.

MITAuto-check passedDevOps & Cloud

Install Gamma Incident Runbook

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill gamma-incident-runbook -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace gamma-incident-runbook --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/gamma-incident-runbook .claude/skills/gamma-incident-runbook && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gamma-incident-runbook
GitHub stars
2.8k
Token cost
~1.7k tokens
SKILL.md length
456 words
Files
1
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Manage incident response for Gamma integration issues. An agent skill from jeremylongshore/tons-of-skills-marketplace.

  • Works in 3 steps: Check Gamma Status → Review Key Metrics → Review Recent Logs
  • Experiencing production incidents
  • SKILL.md covers Instructions, Output, Error Handling and Examples, plus 9 more sections
  • Calls curl and jq; reaches status.gamma.app and api.gamma.app; needs GAMMA_API_KEY

What it does

Gamma Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering Incident response and Runbooks and postmortems. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Experiencing production incidents
  • Need systematic troubleshooting procedures
  • With phrases like gamma incident
  • Gamma emergency

Example prompts

  • “gamma incident”
  • “gamma outage”
  • “gamma down”
  • “/gamma-incident-runbook”

Requirements

  • A credential in GAMMA_API_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(curl:*), Grep

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Check Gamma Status
  2. Review Key Metrics
  3. Review Recent Logs

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(curl:*)
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • status.gamma.app
    • api.gamma.app

    Also links to:

    • gamma.app

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GAMMA_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Gamma Incident Runbook loads about 1.7k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 456 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 456 words, ~1,747 tokens.

Download SKILL.mdSave it as .claude/skills/gamma-incident-runbook/SKILL.md (or your agent's skills folder).
name
gamma-incident-runbook
description
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".
allowed-tools
Read, Write, Edit, Bash(curl:*), Grep
compatibility
Designed for Claude Code
version
1.13.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, gamma, incident-response

Gamma Incident Runbook

Instructions

Assign severity and an opaque incident ID, pause unsafe publishing/sharing, classify the issue, apply the smallest safe mitigation, verify recovery with synthetic content, and record the owner’s decision.

Output

Produce a redacted incident receipt with severity, impact, mitigation, recovery verification, rollback decision, owner, and follow-ups.

Error Handling

Revoke scoped credentials on suspected exposure, do not replay content actions until access/destination checks pass, and keep private content out of incident artifacts.

Examples

During a synthetic sharing outage, pause the staging integration, confirm no duplicate publish occurs, restore one canary, and resume only after the incident owner records recovery evidence.

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

LevelDescriptionResponse TimeEscalation
P1Complete outage, no presentations< 15 minImmediate
P2Degraded, slow or partial failures< 30 min1 hour
P3Minor issues, workaround available< 2 hours4 hours
P4Cosmetic or non-urgent< 24 hoursNone

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_requests_total{status=~"5.."}[5m])' | jq '.data.result'  # 9090: Prometheus port

# Check latency P95
curl -s 'http://prometheus:9090/api/v1/query?query=histogram_quantile(0.95,rate(gamma_request_duration_seconds_bucket[5m]))' | jq '.data.result'  # Prometheus port

# Check rate limit
curl -s 'http://prometheus:9090/api/v1/query?query=gamma_rate_limit_remaining' | jq '.data.result'  # Prometheus port
Step 3: Review Recent Logs
bash
# Last 100 error logs
grep -i "gamma.*error" /var/log/app/gamma-*.log | tail -100

# Rate limit hits
grep "429" /var/log/app/gamma-*.log | wc -l  # HTTP 429 Too Many Requests

# Timeout errors
grep -i "timeout" /var/log/app/gamma-*.log | tail -50

Incident Response Procedures

Scenario 1: API Returning 5xx Errors

Symptoms:

  • High error rate in monitoring
  • Users reporting failed presentations
  • 500/502/503 responses from Gamma

Actions:

  1. Verify Gamma status: https://status.gamma.app

  2. If Gamma outage confirmed:

    • Enable degraded mode / show maintenance message
    • Monitor status page for updates
    • No action needed on our side

  3. If Gamma is operational:

    bash
    # Check our request patterns
grep "5[0-9][0-9]" /var/log/app/gamma-*.log | \
  awk '{print $1}' | sort | uniq -c | sort -rn

# Look for malformed requests
grep -B5 "500" /var/log/app/gamma-*.log | grep "request"

  4. Rollback recent deployments if issue correlates

Scenario 2: Rate Limit Exceeded (429)

Symptoms:

  • 429 responses in logs
  • Rate limit metrics at zero
  • Slow or queued requests

Actions:

  1. Immediate mitigation:

    bash
    # Enable request throttling
curl -X POST http://localhost:8080/admin/throttle \
  -d '{"gamma": {"rps": 10}}'

  2. Check for runaway processes:

    bash
    # Find high-volume clients
grep "gamma" /var/log/app/*.log | \
  awk '{print $5}' | sort | uniq -c | sort -rn | head -20

  3. Enable circuit breaker:

    bash
    curl -X POST http://localhost:8080/admin/circuit-breaker \
  -d '{"service": "gamma", "state": "open"}'

  4. Long-term: Review rate limit tier with Gamma

Show full SKILL.md (204 more words)Show less
Scenario 3: High Latency

Symptoms:

  • Slow presentation creation
  • Timeouts in logs
  • P95 latency > 10s

Actions:

  1. Check Gamma latency vs our latency:

    bash
    # Direct Gamma latency
for i in {1..5}; do
  curl -w "%{time_total}\n" -o /dev/null -s \
    -H "Authorization: Bearer $GAMMA_API_KEY" \
    https://api.gamma.app/v1/ping
done

  2. If Gamma is slow:

    • Increase timeouts temporarily
    • Enable async mode for non-critical operations
    • Queue heavy operations

  3. If our infrastructure is slow:

    • Check CPU/memory on app servers
    • Review connection pool settings
    • Check network connectivity
Scenario 4: Authentication Failures (401/403)

Symptoms:

  • All requests failing with 401
  • "Invalid API key" errors
  • Sudden authentication failures

Actions:

  1. Verify API key:

    bash
    # Test key directly
curl -H "Authorization: Bearer $GAMMA_API_KEY" \
  https://api.gamma.app/v1/ping

# Check key format
echo $GAMMA_API_KEY | head -c 20

  2. If key is invalid:

    • Check if key was rotated
    • Deploy backup key: GAMMA_API_KEY_SECONDARY
    • Generate new key in Gamma dashboard

  3. Notify team and update secrets

Communication Templates

Internal Notification
INCIDENT: Gamma Integration Issue

Severity: P[X]
Status: Investigating / Identified / Mitigating / Resolved
Impact: [Description of user impact]
Start Time: [ISO timestamp]

Summary: [Brief description]

Current Actions:
- [Action 1]
- [Action 2]

Next Update: [Time]
User-Facing Message
We're currently experiencing issues with presentation generation.
Our team is actively working to resolve this.

Workaround: [If available]
Status updates: [Link to status page]
ETA: [If known]

Post-Incident Checklist

  • Incident timeline documented
  • Root cause identified
  • User impact quantified
  • Fix verified in production
  • Monitoring gaps identified
  • Preventive measures documented
  • Post-mortem scheduled (for P1/P2)

Resources

Next Steps

Proceed to gamma-data-handling for data management.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/.curated/gamma-incident-runbook of jeremylongshore/tons-of-skills-marketplace.

Open the folder on GitHubat commit cfae287

Compare with similar skills

Gamma Incident Runbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gamma Incident Runbook compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gamma Incident Runbook this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.7kAutomated safety check: PassMIT
Oncallpigweed-project/pigweed548—~963Automated safety check: PassApache-2.0
Activation Governance Chaos RolloutAli-Marandi/DataSense107—~1.9kAutomated safety check: PassMIT
Incident Response686f6c61/alfred-dev117—~1.1kAutomated safety check: PassMIT
Superset Incident Triagesuperset-sh/superset15k—~1kAutomated safety check: PassCustom licence
Post-Incident DebriefVeryGoodOpenSource/vgv-wingspan109—~1.9kAutomated safety check: PassMIT

Similar skills

  • Oncall

    pigweed-project/pigweed

    Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).

    548 GitHub stars~963 tokensUpdated today
    DevOps & CloudAuto-check passed

  • Activation Governance Chaos Rollout

    Ali-Marandi/DataSense

    Design, validate, and govern fail-closed customer-activation automations that use an Outbox/worker pattern.

    107 GitHub stars~1.9k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Incident Response

    686f6c61/alfred-dev

    Protocolo de respuesta ante incidentes en produccion: triaje, mitigacion, causa raiz y postmortem.

    117 GitHub stars~1.1k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Superset Incident Triage

    superset-sh/superset

    Does a read-only first pass on a possible production incident: gathers deploy, Sentry and health-check signals, proposes a severity and status message, then stops for human approval.

    15k GitHub stars~1k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Post-Incident Debrief

    VeryGoodOpenSource/vgv-wingspan

    Produces a blameless post-incident debrief with timeline, root cause and follow-up actions after an outage, failed release or significant bug, while details are fresh.

    109 GitHub stars~1.9k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed

  • SRE Engineer

    Jeffallan/claude-skills

    Defines SLIs, SLOs and error budgets, and sets up golden-signal monitoring, blameless postmortems, toil automation and chaos experiments for production systems.

    12k GitHub stars~1.7k tokensUpdated 7 days ago
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Gamma Incident Runbook

What does Gamma Incident Runbook do?

Manage incident response for Gamma integration issues. An agent skill from jeremylongshore/tons-of-skills-marketplace. Gamma Incident Runbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Manage incident response for Gamma integration issues.

When should I use Gamma Incident Runbook?

Gamma Incident Runbook fits situations like: experiencing production incidents; need systematic troubleshooting procedures; with phrases like gamma incident; gamma emergency.

How do I install Gamma Incident Runbook in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill gamma-incident-runbook -a claude-code`. Or copy the skill folder (skills/.curated/gamma-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/gamma-incident-runbook in your project. Claude Code loads it when a task matches its description.

How do I install Gamma Incident Runbook in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill gamma-incident-runbook -a codex`. Or copy the skill folder (skills/.curated/gamma-incident-runbook in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/gamma-incident-runbook in your project. Codex loads it when a task matches its description.

Can I use Gamma Incident Runbook in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill gamma-incident-runbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gamma-incident-runbook, .gemini/skills/gamma-incident-runbook, .github/skills/gamma-incident-runbook and .opencode/skills/gamma-incident-runbook in your project.

What does Gamma Incident Runbook need to run?

Going by SKILL.md and its folder, Gamma Incident Runbook needs the command-line tools its instructions call (curl and jq) and credentials named GAMMA_API_KEY. Our summary lists: A credential in GAMMA_API_KEY. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(curl:*), Grep. Compatibility (from SKILL.md): Designed for Claude Code.

Does Gamma Incident Runbook access the network?

SKILL.md names 3 domains. In commands or code: status.gamma.app and api.gamma.app; the agent is likely to contact these when it follows the instructions. As links in the text: gamma.app. This is read from the text; nothing was executed.

Is Gamma Incident Runbook safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gamma Incident Runbook use?

Gamma Incident Runbook is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gamma Incident Runbook use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gamma Incident Runbook?

Skills that share tags, products or a category with Gamma Incident Runbook: Oncall (pigweed-project/pigweed, 548 stars), Activation Governance Chaos Rollout (Ali-Marandi/DataSense, 107 stars), Incident Response (686f6c61/alfred-dev, 117 stars) and Superset Incident Triage (superset-sh/superset, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gamma Incident Runbook?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.