Complete Gamma integration skill pack with 24 skills covering AI presentations, document generation, templates, and visual content creation. Flagship tier vendor pack.

24 Skills

MIT License

Installation

Open Claude Code and run this command:

/plugin install gamma-pack@claude-code-plugins-plus

Use --global to install for all projects, or --project for current project only.

What It Does

> Claude Code skill pack for Gamma.app integration — AI presentation generation (24 skills)

Skills (24)

gamma-ci-integration View full skill →

'Configure Gamma CI/CD integration with GitHub Actions and testing.

ReadWriteEditBash(gh:*)

Gamma CI Integration

Overview

Set up continuous integration for Gamma-powered applications with automated testing and deployment.

Prerequisites

GitHub repository with Actions enabled
Gamma test API key
npm/pnpm project configured

Instructions

Step 1: Create GitHub Actions Workflow


# .github/workflows/gamma-ci.yml
name: Gamma CI

on:
  push:
    branches: [main, develop]
  pull_request:
    branches: [main]

env:
  GAMMA_API_KEY: ${{ secrets.GAMMA_API_KEY }}

jobs:
  test:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v4

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'

      - name: Install dependencies
        run: npm ci

      - name: Run unit tests
        run: npm test

      - name: Run Gamma integration tests
        run: npm run test:gamma
        env:
          GAMMA_MOCK: ${{ github.event_name == 'pull_request' }}

      - name: Upload coverage
        uses: codecov/codecov-action@v4
        with:
          files: ./coverage/lcov.info

Step 2: Create Test Scripts


// package.json
{
  "scripts": {
    "test": "vitest run",
    "test:gamma": "vitest run --config vitest.gamma.config.ts",
    "test:gamma:live": "GAMMA_MOCK=false vitest run --config vitest.gamma.config.ts"
  }
}

Step 3: Gamma Test Configuration


// vitest.gamma.config.ts
import { defineConfig } from 'vitest/config';

export default defineConfig({
  test: {
    include: ['tests/gamma/**/*.test.ts'],
    testTimeout: 60000, // Gamma API can be slow  # 60000: 1 minute in ms
    hookTimeout: 30000,  # 30000: 30 seconds in ms
    setupFiles: ['./tests/gamma/setup.ts'],
  },
});

Step 4: Test Setup with Mocking


// tests/gamma/setup.ts
import { beforeAll } from 'vitest';
import { createGammaClient, type GammaClient } from '../../src/client';

const useMock = process.env.GAMMA_MOCK === 'true';

export let gamma: ReturnType<typeof createGammaClient>;

beforeAll(() => {
  if (useMock) {
    gamma = createMockGammaClient();
  } else {
    gamma = createGammaClient({
      apiKey: process.env.GAMMA_API_KEY!,
    });
  }
});

function createMockGammaClient() {
  return {
    generate: vi.fn().mockResolvedValue({ generationId: 'mock-gen-id' }),
    poll: vi.fn().mockResolvedValue({
      status: 'completed',
      gammaUrl: 'https://gamma.app/docs/mock-test',
      exportUrl: 'https://export.gamma.app/mock.pdf',
      creditsUsed: 10,
    }),
    listThemes: vi.fn().mockResolvedValue([{ id: 'theme_1', name: 'Default


                
                  
                  gamma-common-errors
                  View full skill →
                
                
                  'Debug and resolve common Gamma API errors.
                  
                      ReadWriteEditGrep
                    
                
                
                  Gamma Common Errors
Overview
Reference guide for debugging and resolving common Gamma API errors.
Prerequisites

Active Gamma integration
Access to logs and error messages
Understanding of HTTP status codes

Error Reference
Authentication Errors (401/403)

// Error: Invalid API Key
{
  "error": "unauthorized",
  "message": "Invalid or expired API key"
}

Solutions:

Verify API key in Gamma dashboard
Check environment variable is set: echo $GAMMAAPIKEY
Ensure key hasn't been rotated
Check for trailing whitespace in key

Rate Limit Errors (429)

// Error: Rate Limited
{
  "error": "rate_limited",
  "message": "Too many requests",
  "retry_after": 60
}

Solutions:

Implement exponential backoff
Check rate limit headers: X-RateLimit-Remaining
Upgrade plan for higher limits
Queue requests with delays


async function withRetry(fn: () => Promise<any>, maxRetries = 3) {
  for (let i = 0; i < maxRetries; i++) {
    try {
      return await fn();
    } catch (err) {
      if (err.code === 'rate_limited' && i < maxRetries - 1) {
        const delay = (err.retryAfter || Math.pow(2, i)) * 1000;  # 1000: 1 second in ms
        await new Promise(r => setTimeout(r, delay));
        continue;
      }
      throw err;
    }
  }
}

Generation Errors (400/500)

// Error: Generation Failed
{
  "error": "generation_failed",
  "message": "Unable to generate presentation",
  "details": "Content too complex"
}

Solutions:

Simplify prompt or reduce slide count
Remove special characters from content
Check content length limits
Try different style setting

Timeout Errors

// Error: Request Timeout
{
  "error": "timeout",
  "message": "Request timed out after 30000ms"
}

Solutions:

Increase client timeout setting
Use async job pattern for large presentations
Check network connectivity
Reduce request complexity


const gamma = new GammaClient({
  apiKey: process.env.GAMMA_API_KEY,
  timeout: 60000, // 60 seconds  # 60000: 1 minute in ms
});

Export Errors

// Error: Export Failed
{
  "error": "export_f


                
                  
                  gamma-core-workflow-a
                  View full skill →
                
                
                  'Generate presentations, documents, and webpages via Gamma API.
                  
                      ReadWriteEditBash(curl:*)Bash(node:*)
                    
                
                
                  Gamma Core Workflow A: Content Generation
Overview
Generate presentations, documents, webpages, and social posts using Gamma's Generate API (POST /v1.0/generations). This skill covers the full parameter set: content, output format, text mode, text amount, themes, image options, sharing, folders, and export format.
Prerequisites

Completed gamma-sdk-patterns (client wrapper ready)
Pro account with available credits
Workspace themes configured (optional)

API Parameters Reference

Parameter
Type
Options
Default


content
string
Your text/prompt
Required


outputFormat
string
presentation, document, webpage, social_post
presentation


textMode
string
generate, condense, preserve
generate


textAmount
string
brief, medium, detailed, extensive
medium


themeId
string
From GET /v1.0/themes
Workspace default


imageOptions.style
string
Free text (e.g., "photorealistic", "watercolor illustration")
AI default


exportAs
string
pdf, pptx, png
None (no auto-export)


sharingOptions
object
workspaceAccess, externalAccess
Workspace defaults


folderIds
string[]
From GET /v1.0/folders
Root folder


Instructions
Step 1: Basic Presentation Generation

import { createGammaClient, pollUntilDone } from "./lib/gamma";

const gamma = createGammaClient({ apiKey: process.env.GAMMA_API_KEY! });

// Simple generation — just content and format
const { generationId } = await gamma.generate({
  content: "Create a 10-card pitch deck for a sustainable energy startup",
  outputFormat: "presentation",
});

const result = await pollUntilDone(gamma, generationId);
console.log(`View: ${result.gammaUrl}`);

Step 2: Full Parameter Generation

// Use all available parameters for precise control
async function generateFullControl() {
  // First, discover workspace themes
  const themes = await gamma.listThemes();
  const corporateTheme = themes.find((t)


                
                  
                  gamma-core-workflow-b
                  View full skill →
                
                
                  'Generate from templates, retrieve exports, and manage sharing via Gamma.
                  
                      ReadWriteEditBash(curl:*)Bash(node:*)
                    
                
                
                  Gamma Core Workflow B: Templates & Export
Overview
Use Gamma's template-based generation (POST /v1.0/generations/from-template) and export retrieval (GET /v1.0/generations/{id}/files) endpoints. Template generation lets you replicate a single-page gamma template across multiple variations. Export retrieval gives you downloadable PDF, PPTX, and PNG files.
Prerequisites

Completed gamma-core-workflow-a
A template gamma with exactly one page (created in the Gamma app)
Understanding of the generate-poll-retrieve pattern

Key Concepts

Template gamma: A regular gamma with exactly one page, used as a repeatable template
gammaId: Found in the gamma URL or copied from the app
Export URLs: Temporary download links returned after generation — download promptly as they expire

Instructions
Step 1: Create from Template

import { createGammaClient, pollUntilDone } from "./lib/gamma";

const gamma = createGammaClient({ apiKey: process.env.GAMMA_API_KEY! });

// POST /v1.0/generations/from-template
// The template gamma MUST have exactly one page
async function generateFromTemplate(
  templateGammaId: string,
  prompt: string,
  options: {
    themeId?: string;
    exportAs?: "pdf" | "pptx" | "png";
    imageStyle?: string;
  } = {}
) {
  const { generationId } = await gamma.generateFromTemplate({
    gammaId: templateGammaId,
    prompt,
    themeId: options.themeId,
    exportAs: options.exportAs,
    imageOptions: options.imageStyle
      ? { style: options.imageStyle }
      : undefined,
  });

  return pollUntilDone(gamma, generationId);
}

// Usage: generate a sales proposal from a template
const result = await generateFromTemplate(
  "gamma_template_abc123",   // Your one-page template ID
  "Create a sales proposal for Acme Corp. Highlight our cloud migration services, 99.9% uptime SLA, and 24/7 support.",
  { exportAs: "pdf", imageStyle: "corporate professional" }
);

console.log(`View: ${result.gammaUrl}`);
console.log(`Download: ${result.exportUrl}`);

Step 2: Batch Template Generation

// Generate multiple variations from the same template
const clients = [
  { name: "Acme Corp", focus: "cloud migration" },
  { name: "TechStart Inc", focus: "AI implementation" },
  { name: "GlobalBank", focus: "security compliance" },
];

import pLimit from "p-limit";
const limit = pLimit(2); // Respect rate limits

const proposals = await Promise.allSettled(
  clients.map((client) =>
    limit(() =>
      generateFromTemplate(
        "gamma_template_abc123",
        `Proposal for ${client.name}


                
                  
                  gamma-cost-tuning
                  View full skill →
                
                
                  'Optimize Gamma usage costs and manage API spending.
                  
                      ReadWriteEdit
                    
                
                
                  Gamma Cost Tuning
Overview
Optimize Gamma API usage to minimize credit consumption. Gamma uses a credit-based billing system where costs are driven by image generation model tier and content complexity. API access requires Pro or higher subscription.
Prerequisites

Active Gamma Pro/Ultra/Teams/Business subscription
Understanding of credit system
Completed gamma-install-auth setup

Gamma Credit System
Image Model Tiers

Tier
Credits per Image
Quality Level


Standard
2-15
Good for internal/draft presentations


Advanced
20-33
Higher quality, more detail


Premium
34-75
Best quality images


Ultra
30-125
Highest fidelity, photorealistic


Card text generation also costs credits based on the AI model used.
Plan Comparison

Feature
Pro
Ultra
Teams
Business


Monthly credits
Included
More credits
Team pool
Custom


API access
Yes
Yes
Yes
Yes


Max cards
Standard
Up to 75
Standard
Custom


Ad-hoc credit purchase
Yes
Yes
Yes
Yes


Auto-recharge
Yes
Yes
Yes
Yes


Instructions
Step 1: Track Credit Usage

// src/gamma/cost-tracker.ts
interface UsageEntry {
  generationId: string;
  creditsUsed: number;
  outputFormat: string;
  timestamp: Date;
}

class CreditTracker {
  private usage: UsageEntry[] = [];

  record(entry: UsageEntry) {
    this.usage.push(entry);
  }

  getDaily(): { total: number; count: number; avg: number } {
    const today = new Date().toDateString();
    const todayUsage = this.usage.filter(
      (u) => u.timestamp.toDateString() === today
    );
    const total = todayUsage.reduce((sum, u) => sum + u.creditsUsed, 0);
    return {
      total,
      count: todayUsage.length,
      avg: todayUsage.length > 0 ? Math.round(total / todayUsage.length) : 0,
    };
  }

  getMonthly(): { total: number; count: number } {
    const thisMonth = new Date().getMonth();
    const monthUsage = this.usage.filter(
      (u) => u.timestamp.getMonth() === thisMonth
    );
    return {
      total: monthUsage.reduce((sum, u) => sum + u.creditsUsed, 0),
      count: monthUsage.length,
    };
  }
}

// Track after each generation
const tracker = new CreditTracker();

async function generateTracked(gamma: GammaClient, request: GenerateRequest) {
  const { generationId } = await gamma.generate


                
                  
                  gamma-data-handling
                  View full skill →
                
                
                  'Handle data privacy, retention, and compliance for Gamma integrations.
                  
                      ReadWriteEdit
                    
                
                
                  Gamma Data Handling
Overview
Data handling, privacy controls, and compliance for Gamma API integrations. Gamma processes user-submitted content through AI to generate presentations -- understand what data flows where and how to handle PII, retention, and GDPR requirements.
Prerequisites

Understanding of data privacy regulations (GDPR, CCPA)
Completed gamma-install-auth setup
Data classification policies defined

Data Flow Map

User Input (content, prompts)
     │
     ▼
┌──────────────┐
│  Your App    │  ← PII may be in content (names, company data)
│  (API key)   │
└──────┬───────┘
       │ POST /v1.0/generations
       ▼
┌──────────────┐
│  Gamma API   │  ← Content processed by AI
│  (gamma.app) │  ← Images generated
└──────┬───────┘
       │ gammaUrl + exportUrl
       ▼
┌──────────────┐
│  Generated   │  ← Presentation stored in Gamma workspace
│  Content     │  ← Export files (PDF/PPTX/PNG) temporary
└──────────────┘

Data Classification

Data Type
Classification
Where Stored
Retention


API key
Secret
Your env vars
Active use only


Content/prompts
May contain PII
Gamma servers (during generation)
Gamma's policy


Generated gammas
User data
Gamma workspace
User-controlled


Export files (PDF/PPTX)
User data
Temporary URLs
Download promptly, URLs expire


User prompts in logs
PII risk
Your infrastructure
Your policy (sanitize!)


Credit usage
Billing data
Gamma
Per Gamma ToS


Instructions
Step 1: Sanitize Content Before Sending

// src/gamma/sanitize.ts
// Remove PII from content before sending to Gamma if not needed

interface SanitizeOptions {
  removeEmails: boolean;
  removePhones: boolean;
  maskNames: boolean;
}

function sanitizeContent(content: string, opts: SanitizeOptions): string {
  let sanitized = content;

  if (opts.removeEmails) {
    sanitized = sanitized.replace(/[\w.-]+@[\w.-]+\.\w+/g, "[email]");
  }
  if (opts.removePhones) {
    sanitized = sanitized.replace(/\+?[\d\s()-]{10,}/g, "[phone]");
  }
  if (opts.maskNames) {
    // Only mask if you have a list of known names
    // Generic regex would be too aggressive
  }

  return sanitized;
}

// Usage: sanitize before generation
const safeContent = sanitizeContent(userContent, {
  removeEmails: true,
  removePhones: true,
  maskNames: false,
});

await gamma.generate({
  content: safeContent,
  outputFormat: "presentation",
});

Step 2: Sanitize Logs

// src/


                
                  
                  gamma-debug-bundle
                  View full skill →
                
                
                  'Comprehensive debugging toolkit for Gamma integration issues.
                  
                      ReadWriteEditBash(node:*)Grep
                    
                
                
                  Gamma Debug Bundle
Current State
!node --version 2>/dev/null || echo 'N/A'
!python3 --version 2>/dev/null || echo 'N/A'
!uname -a
Overview
Debugging toolkit for Gamma API integration issues. Includes connectivity tests, request tracing, diagnostic scripts, and support ticket templates. Gamma uses a REST API at https://public-api.gamma.app/v1.0/ with X-API-KEY header authentication.
Prerequisites

Active Gamma integration
Node.js 18+ or Python 3.10+
curl and jq available

Instructions
Step 1: Quick Connectivity Test (curl)

#!/bin/bash
set -euo pipefail
echo "=== Gamma API Diagnostic ==="

# 1. Check API key
if [ -z "${GAMMA_API_KEY:-}" ]; then
  echo "FAIL: GAMMA_API_KEY not set"; exit 1
fi
echo "OK: API key set (${#GAMMA_API_KEY} chars, prefix: ${GAMMA_API_KEY:0:4}...)"

# 2. Test authentication via /themes endpoint
STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
  -H "X-API-KEY: $GAMMA_API_KEY" \
  "https://public-api.gamma.app/v1.0/themes")
if [ "$STATUS" = "200" ]; then
  echo "OK: Authentication successful"
elif [ "$STATUS" = "401" ]; then
  echo "FAIL: Invalid API key (401)"
elif [ "$STATUS" = "403" ]; then
  echo "FAIL: Account not on Pro+ plan (403)"
else
  echo "WARN: Unexpected status $STATUS"
fi

# 3. Check latency
echo "--- Latency (3 samples) ---"
for i in 1 2 3; do
  LATENCY=$(curl -s -o /dev/null -w "%{time_total}" \
    -H "X-API-KEY: $GAMMA_API_KEY" \
    "https://public-api.gamma.app/v1.0/themes")
  echo "  Request $i: ${LATENCY}s"
done

# 4. List themes (verify API access)
echo "--- Workspace Themes ---"
curl -s -H "X-API-KEY: $GAMMA_API_KEY" \
  "https://public-api.gamma.app/v1.0/themes" | jq '.[].name' 2>/dev/null || echo "Could not parse themes"

Step 2: TypeScript Diagnostic Script

// scripts/gamma-diagnose.ts
const BASE = "https://public-api.gamma.app/v1.0";
const headers = {
  "X-API-KEY": process.env.GAMMA_API_KEY!,
  "Content-Type": "application/json",
};

interface TestResult {
  test: string;
  status: "PASS" | "FAIL";
  detail: string;
  latencyMs?: number;
}

async function diagnose(): Promise<TestResult[]> {
  const results: TestResult[] = [];

  // Test 1: API key set
  if (!process.env.GAMMA_API_KEY) {
    results.push({ test: "API Key", status: "FAIL", detail: "GAMMA_API_KEY not set" });
    return results;
  }
  results.push({
    test: "API Key",


                
                  
                  gamma-deploy-integration
                  View full skill →
                
                
                  'Deploy Gamma-integrated applications to production environments.
                  
                      ReadWriteEditBash(vercel:*)Bash(aws:*)Bash(gcloud:*)
                    
                
                
                  Gamma Deploy Integration
Overview
Deploy Gamma-integrated applications to various cloud platforms with proper configuration and secret management.
Prerequisites

Completed CI integration
Cloud platform account (Vercel, AWS, or GCP)
Production Gamma API key

Instructions
Vercel Deployment
Step 1: Configure Vercel Project

set -euo pipefail
# Install Vercel CLI
npm i -g vercel

# Link project
vercel link

# Set environment variable
vercel env add GAMMA_API_KEY production

Step 2: Create vercel.json

{
  "framework": "nextjs",
  "buildCommand": "npm run build",
  "env": {
    "GAMMA_API_KEY": "@gamma_api_key"
  },
  "functions": {
    "api/**/*.ts": {
      "maxDuration": 30
    }
  }
}

Step 3: Deploy

# Preview deployment
vercel

# Production deployment
vercel --prod

AWS Lambda Deployment
Step 1: Store Secret in AWS Secrets Manager

aws secretsmanager create-secret \
  --name gamma/api-key \
  --secret-string '{"apiKey":"your-gamma-api-key"}'

Step 2: Lambda Configuration

// lambda/gamma-handler.ts
import { SecretsManager } from '@aws-sdk/client-secrets-manager';
import { GammaClient } from '@gamma/sdk';

const secretsManager = new SecretsManager({ region: 'us-east-1' });
let gamma: GammaClient;

async function getGammaClient() {
  if (!gamma) {
    const secret = await secretsManager.getSecretValue({
      SecretId: 'gamma/api-key',
    });
    const { apiKey } = JSON.parse(secret.SecretString!);
    gamma = new GammaClient({ apiKey });
  }
  return gamma;
}

export async function handler(event: any) {
  const client = await getGammaClient();
  const result = await client.presentations.create({
    title: event.title,
    prompt: event.prompt,
  });
  return { statusCode: 200, body: JSON.stringify(result) };  # HTTP 200 OK
}

Step 3: SAM Template

# template.yaml
AWSTemplateFormatVersion: '2010-09-09'  # 2010 = configured value
Transform: AWS::Serverless-2016-10-31  # 2016 = configured value

Resources:
  GammaFunction:
    Type: AWS::Serverless::Function
    Properties:
      Handler: dist/gamma-handler.handler
      Runtime: nodejs20.x
      Timeout: 30
      MemorySize: 256  # 256 bytes
      Policies:
        - SecretsManagerReadWrite
      Environment:
        Variables:
          NODE_ENV: production

Google Cloud Run Deployment
Step 1: Store Secret

echo -n "your-gamma-api-key" | \
  gcloud secrets create gamma-api-key --d


                
                  
                  gamma-enterprise-rbac
                  View full skill →
                
                
                  'Implement enterprise role-based access control for Gamma integrations.
                  
                      ReadWriteEdit
                    
                
                
                  Gamma Enterprise RBAC
Overview
Implement role-based access control for Gamma API integrations. Gamma's API uses a single API key per workspace -- granular permissions must be implemented in your application layer. The Teams and Business plans support workspace-level collaboration with shared themes and folders.
Prerequisites

Gamma Teams or Business subscription
Application database for user/role storage
Completed gamma-install-auth setup

Gamma Access Model

Gamma Workspace (1 API key)
├── Themes (shared across workspace)
├── Folders (shared across workspace)
└── Generations (tied to API key, not individual users)

Your Application Layer (you implement this):
├── Organization
│   ├── Admin (manage API key, configure themes)
│   ├── Editor (generate presentations, use templates)
│   ├── Viewer (view generated presentations, download exports)
│   └── Guest (no generation access)

Key point: Gamma's API does not have per-user authentication. All API calls use the workspace API key. You must enforce per-user permissions in your application.
Instructions
Step 1: Define Role Hierarchy

// src/auth/gamma-roles.ts
type GammaRole = "guest" | "viewer" | "editor" | "admin";

const PERMISSIONS: Record<GammaRole, string[]> = {
  guest: [],
  viewer: ["generation:view", "export:download"],
  editor: ["generation:view", "generation:create", "export:download", "template:use"],
  admin: [
    "generation:view", "generation:create", "export:download",
    "template:use", "template:manage", "theme:manage",
    "settings:manage", "member:manage",
  ],
};

function hasPermission(role: GammaRole, permission: string): boolean {
  return PERMISSIONS[role]?.includes(permission) ?? false;
}

Step 2: Authorization Middleware

// src/middleware/gamma-auth.ts
import { Request, Response, NextFunction } from "express";

function requireGammaPermission(permission: string) {
  return (req: Request, res: Response, next: NextFunction) => {
    const user = req.user; // Set by your auth middleware
    if (!user) return res.status(401).json({ error: "Unauthorized" });

    if (!hasPermission(user.gammaRole, permission)) {
      return res.status(403).json({
        error: "Forbidden",
        required: permission,
        userRole: user.gammaRole,
      });
    }
    next();
  };
}

// Usage
app.post("/api/presentations",
  requireGammaPermission("generation:create"),
  async (req, res) => {
    const gamma = createGammaClient({ apiKey: process.env.GAMMA_API_KEY! });
    const { generationId } = await


                
                  
                  gamma-hello-world
                  View full skill →
                
                
                  'Generate your first Gamma presentation via the API.
                  
                      ReadWriteEditBash(curl:*)Bash(node:*)
                    
                
                
                  Gamma Hello World
Overview
Generate your first presentation using Gamma's async Generate API. The workflow is: POST to create a generation, poll for status, then retrieve results (gammaUrl + exportUrl).
Prerequisites

Completed gamma-install-auth setup
Valid GAMMAAPIKEY environment variable
Pro account with available credits

The Generate-Poll-Retrieve Pattern
All Gamma generations are asynchronous:

POST /v1.0/generations — submit content, receive generationId
GET /v1.0/generations/{generationId} — poll every 5s until completed or failed
Result — gammaUrl (view in app) + exportUrl (download PDF/PPTX/PNG)

Instructions
Minimal curl Example

# Step 1: Create generation
GENERATION=$(curl -s -X POST \
  "https://public-api.gamma.app/v1.0/generations" \
  -H "X-API-KEY: ${GAMMA_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Create a 5-card presentation about the benefits of AI in business",
    "outputFormat": "presentation"
  }')

GEN_ID=$(echo "$GENERATION" | jq -r '.generationId')
echo "Generation started: $GEN_ID"

# Step 2: Poll until complete (every 5 seconds)
while true; do
  STATUS=$(curl -s \
    "https://public-api.gamma.app/v1.0/generations/${GEN_ID}" \
    -H "X-API-KEY: ${GAMMA_API_KEY}")
  STATE=$(echo "$STATUS" | jq -r '.status')
  echo "Status: $STATE"
  [ "$STATE" = "completed" ] || [ "$STATE" = "failed" ] && break
  sleep 5
done

# Step 3: Retrieve results
echo "$STATUS" | jq '{gammaUrl, exportUrl, creditsUsed}'

Node.js / TypeScript Example

const GAMMA_BASE = "https://public-api.gamma.app/v1.0";
const headers = {
  "X-API-KEY": process.env.GAMMA_API_KEY!,
  "Content-Type": "application/json",
};

async function generatePresentation(content: string) {
  // Step 1: Create generation
  const createRes = await fetch(`${GAMMA_BASE}/generations`, {
    method: "POST",
    headers,
    body: JSON.stringify({
      content,
      outputFormat: "presentation",
    }),
  });
  if (!createRes.ok) throw new Error(`Create failed: ${createRes.status}`);
  const { generationId } = await createRes.json();
  console.log(`Generation started: ${generationId}`);

  // Step 2: Poll for completion
  while (true) {
    const pollRes = await fetch(`${GAMMA_BASE}/generations/${generationId}`, { headers });
    const result = await pollRes.json();

    if (res


                
                  
                  gamma-incident-runbook
                  View full skill →
                
                
                  'Manage incident response for Gamma integration issues.
                  
                      ReadWriteEditBash(curl:*)Grep
                    
                
                
                  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

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

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

# 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:

Verify Gamma status: https://status.gamma.app
If Gamma outage confirmed:


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


If Gamma is operational:


                
              

                
                  
                  gamma-install-auth
                  View full skill →
                
                
                  'Set up Gamma API v1.
                  
                      ReadWriteEditBash(curl:*)Bash(npm:*)Bash(pip:*)
                    
                
                
                  Gamma Install & Auth
Overview
Configure authentication for the Gamma Generate API v1.0 (GA since Nov 2025). Gamma uses a REST API at https://public-api.gamma.app/v1.0/ — there is no official SDK package. All requests authenticate via the X-API-KEY header.
Prerequisites

Gamma Pro account or higher (API access requires Pro+)
Node.js 18+ or Python 3.10+ for wrapper code
curl or HTTP client library

Instructions
Step 1: Generate API Key

Log in at gamma.app
Navigate to Settings and Members (dropdown, upper-left)
Select the API key tab
Click Create API key
Copy and securely store the key — it will not be shown again

Step 2: Configure Environment

# Set environment variable (add to .env or shell profile)
export GAMMA_API_KEY="gma_your_api_key_here"

# .env file approach
echo 'GAMMA_API_KEY=gma_your_api_key_here' >> .env

Step 3: Verify Connection

# Quick verification with curl
curl -s -o /dev/null -w "%{http_code}" \
  -H "X-API-KEY: ${GAMMA_API_KEY}" \
  https://public-api.gamma.app/v1.0/themes
# 200 = authenticated, 401 = invalid key

Step 4: First API Call (Node.js)

// gamma-client.ts — thin wrapper around the REST API
const GAMMA_BASE = "https://public-api.gamma.app/v1.0";

interface GammaConfig {
  apiKey: string;
  baseUrl?: string;
}

export function createGammaClient(config: GammaConfig) {
  const headers = {
    "X-API-KEY": config.apiKey,
    "Content-Type": "application/json",
  };
  const base = config.baseUrl ?? GAMMA_BASE;

  return {
    async listThemes() {
      const res = await fetch(`${base}/themes`, { headers });
      if (!res.ok) throw new Error(`Gamma API ${res.status}: ${await res.text()}`);
      return res.json();
    },
    async listFolders() {
      const res = await fetch(`${base}/folders`, { headers });
      if (!res.ok) throw new Error(`Gamma API ${res.status}: ${await res.text()}`);
      return res.json();
    },
  };
}

// Verify connection
const gamma = createGammaClient({ apiKey: process.env.GAMMA_API_KEY! });
const themes = await gamma.listThemes();
console.log(`Connected — ${themes.length} workspace themes available`);

Step 5: First API Call (Python)

import os, requests

GAMMA_BASE = "https://public-api.gamma.app/v1.0"
HEADERS = {
    "X-API-KEY": os.environ["GAMMA_API_KEY"],
    "Content-Type": "application/json",
}

# Verify connection
resp = requests.get(f"{GAMMA_BASE}/themes", headers=HEADERS)
resp.raise_for_st

                

              

                
                  
                  gamma-local-dev-loop
                  View full skill →
                
                
                  'Set up local development workflow for Gamma API integration.
                  
                      ReadWriteEditBash(curl:*)Bash(node:*)Bash(npm:*)
                    
                
                
                  Gamma Local Dev Loop
Overview
Set up an efficient local development workflow for Gamma API integrations. Since Gamma is a REST API with no SDK, the dev loop centers on HTTP request/response testing, mock servers for offline development, and a reusable client wrapper.
Prerequisites

Completed gamma-install-auth setup
Node.js 18+ with tsx for TypeScript execution
GAMMAAPIKEY in .env

Instructions
Step 1: Project Structure

gamma-integration/
├── src/
│   ├── client.ts          # Reusable Gamma API client
│   ├── generate.ts        # Generation workflows
│   └── poll.ts            # Polling helper
├── test/
│   ├── mock-server.ts     # Local mock for offline dev
│   └── integration.test.ts
├── .env                   # GAMMA_API_KEY (gitignored)
├── .env.example           # Template without secrets
├── package.json
└── tsconfig.json

Step 2: Reusable Client Wrapper

// src/client.ts
import "dotenv/config";

const GAMMA_BASE = "https://public-api.gamma.app/v1.0";

export interface GammaClient {
  generate(body: GenerateRequest): Promise<GenerateResponse>;
  poll(generationId: string): Promise<PollResponse>;
  listThemes(): Promise<Theme[]>;
  listFolders(): Promise<Folder[]>;
}

export function createClient(apiKey?: string, baseUrl?: string): GammaClient {
  const key = apiKey ?? process.env.GAMMA_API_KEY;
  if (!key) throw new Error("GAMMA_API_KEY required");
  const base = baseUrl ?? GAMMA_BASE;
  const headers = { "X-API-KEY": key, "Content-Type": "application/json" };

  async function request(method: string, path: string, body?: unknown) {
    const res = await fetch(`${base}${path}`, {
      method,
      headers,
      body: body ? JSON.stringify(body) : undefined,
    });
    if (!res.ok) {
      const text = await res.text();
      throw new Error(`Gamma ${res.status}: ${text}`);
    }
    return res.json();
  }

  return {
    generate: (body) => request("POST", "/generations", body),
    poll: (id) => request("GET", `/generations/${id}`),
    listThemes: () => request("GET", "/themes"),
    listFolders: () => request("GET", "/folders"),
  };
}

Step 3: Poll Helper with Timeout

// src/poll.ts
import type { GammaClient } from "./client";

export async function waitForCompletion(
  client: GammaClient,
  generationId: string,
  opts = { intervalMs: 5000, timeoutMs: 120000 }
) {
  const deadline = Date.now() + opts.timeoutMs;
  while (Date.now() < deadline) {
    const result = await client.poll(generationId);
    if (result.status === "completed") return result;
    if (result.status === &q

                

              

                
                  
                  gamma-migration-deep-dive
                  View full skill →
                
                
                  'Deep dive into migrating to Gamma from other presentation platforms.
                  
                      ReadWriteEditBash(node:*)
                    
                
                
                  Gamma Migration Deep Dive
Current State
!npm list 2>/dev/null | head -10
Overview
Migrate presentation workflows from PowerPoint, Google Slides, Canva, or other platforms to Gamma's AI-powered generation. Gamma takes a fundamentally different approach -- instead of manually placing slides, you provide content and Gamma generates the presentation. Migration is about converting your content pipeline, not your slide files.
Prerequisites

Gamma API access (Pro+ plan)
Source presentations accessible for content extraction
Node.js 18+ for migration scripts
Completed gamma-install-auth setup

Migration Approaches

Approach
When to Use
Effort


Content extraction + regeneration
Lots of text-heavy presentations
Medium


Import via Gamma UI
One-off migration of key decks
Low


Template recreation
Repeatable presentation formats
Medium


Parallel operation
Gradual transition over time
Low


Key insight: You don't "import" slides into Gamma. You extract content from old presentations and regenerate them using Gamma's AI. This often produces better results than the originals.
Instructions
Step 1: Inventory Source Presentations

// scripts/inventory-presentations.ts
import { readdir, stat } from "node:fs/promises";
import { join, extname } from "node:path";

interface PresentationInfo {
  path: string;
  format: string;
  sizeMB: number;
  lastModified: Date;
}

async function inventoryPresentations(dir: string): Promise<PresentationInfo[]> {
  const entries = await readdir(dir, { recursive: true });
  const presentations: PresentationInfo[] = [];

  for (const entry of entries) {
    const ext = extname(entry).toLowerCase();
    if ([".pptx", ".ppt", ".key", ".pdf", ".md"].includes(ext)) {
      const fullPath = join(dir, entry);
      const info = await stat(fullPath);
      presentations.push({
        path: fullPath,
        format: ext,
        sizeMB: info.size / (1024 * 1024),
        lastModified: info.mtime,
      });
    }
  }

  console.log(`Found ${presentations.length} presentations:`);
  const byFormat = presentations.reduce((acc, p) => {
    acc[p.format] = (acc[p.format] || 0) + 1;
    return acc;
  }, {} as Record<string, number>);
  console.log("By format:", byFormat);

  return presentations;
}

Step 2: Extract Content from PowerPoint

// scripts/extract-pptx.ts
// Use 'pptx-parser' or 'officegen' to extract text content

import JSZip from "jszip&quo

                

              

                
                  
                  gamma-multi-env-setup
                  View full skill →
                
                
                  'Configure Gamma across development, staging, and production environments.
                  
                      ReadWriteEditBash(aws:*)Bash(gcloud:*)Bash(vault:*)
                    
                
                
                  Gamma Multi-Environment Setup
Overview
Configure Gamma API access across development, staging, and production environments. Since Gamma is a SaaS API with no self-hosted option, environment separation is achieved through separate workspaces (API keys), mock servers for development, and environment-aware client configuration.
Prerequisites

Separate Gamma workspaces (or at minimum separate API keys) per environment
Secret management solution
Completed gamma-install-auth setup

Environment Architecture

┌─────────────────────────────────────────────────────────┐
│  Development                                             │
│  API: localhost:9876 (mock server) or Gamma API          │
│  Key: GAMMA_API_KEY=gma_dev_xxx                         │
│  Mock: enabled (no credits consumed)                     │
├─────────────────────────────────────────────────────────┤
│  Staging                                                 │
│  API: public-api.gamma.app (separate workspace)         │
│  Key: GAMMA_API_KEY=gma_stg_xxx                         │
│  Mock: disabled                                          │
├─────────────────────────────────────────────────────────┤
│  Production                                              │
│  API: public-api.gamma.app (production workspace)       │
│  Key: GAMMA_API_KEY=gma_prod_xxx (from secret manager)  │
│  Mock: disabled                                          │
└─────────────────────────────────────────────────────────┘

Instructions
Step 1: Environment Configuration

// src/config/gamma.ts
interface GammaEnvConfig {
  apiKey: string;
  baseUrl: string;
  useMock: boolean;
  timeoutMs: number;
  maxRetries: number;
}

function getGammaConfig(): GammaEnvConfig {
  const env = process.env.NODE_ENV ?? "development";

  const configs: Record<string, Partial<GammaEnvConfig>> = {
    development: {
      baseUrl: process.env.GAMMA_MOCK === "true"
        ? "http://localhost:9876/v1.0"
        : "https://public-api.gamma.app/v1.0",
      useMock: process.env.GAMMA_MOCK === "true",
      timeoutMs: 60000,
      maxRetries: 1,
    },
    staging: {
      baseUrl: "https://public-api.gamma.app/v1.0",
      useMock: false,
      timeoutMs: 30000,
      maxRetries: 3,
    },
    production: {
      baseUrl: "https://public-api.gamma.app/v1.0",
      useMock: false,
      timeoutMs: 30000,
      maxRetries: 5,
    },
  };

  const apiKey = process.env.GAMMA_API_KEY;
  if (!apiKey && !configs[env]?.useMock) {
    throw new Error(`GAMMA_API_KEY required for ${env} environment`);
  }

  return {
    apiKey: apiKey ?? "mock-key",
    ...configs[env],
  } as GammaEnvConfig;
}

export const gammaConfig = getGammaConfig();

Step 2: Environment-Aware Client 
                
              

                
                  
                  gamma-observability
                  View full skill →
                
                
                  'Implement comprehensive observability for Gamma integrations.
                  
                      ReadWriteEdit
                    
                
                
                  Gamma Observability
Overview
Implement monitoring, logging, and health checks for Gamma API integrations. Since Gamma does not expose rate limit headers or internal metrics, observability is built around your API call patterns, latency, error rates, credit consumption, and generation success rates.
Prerequisites

Working Gamma integration (see gamma-sdk-patterns)
Monitoring stack (Prometheus/Grafana, Datadog, or CloudWatch)
Logging infrastructure

Instructions
Step 1: Instrumented Client

// src/observability/gamma-metrics.ts
interface GammaMetrics {
  requests: number;
  errors: number;
  generations: number;
  completions: number;
  failures: number;
  totalCredits: number;
  totalLatencyMs: number;
  errorsByStatus: Record<number, number>;
}

const metrics: GammaMetrics = {
  requests: 0, errors: 0,
  generations: 0, completions: 0, failures: 0,
  totalCredits: 0, totalLatencyMs: 0,
  errorsByStatus: {},
};

export function createInstrumentedClient(apiKey: string) {
  const base = "https://public-api.gamma.app/v1.0";
  const headers = { "X-API-KEY": apiKey, "Content-Type": "application/json" };

  async function instrumentedRequest(method: string, path: string, body?: unknown) {
    metrics.requests++;
    const start = Date.now();

    try {
      const res = await fetch(`${base}${path}`, {
        method, headers,
        body: body ? JSON.stringify(body) : undefined,
      });
      metrics.totalLatencyMs += Date.now() - start;

      if (!res.ok) {
        metrics.errors++;
        metrics.errorsByStatus[res.status] = (metrics.errorsByStatus[res.status] || 0) + 1;
        throw new Error(`Gamma ${res.status}: ${await res.text()}`);
      }
      return res.json();
    } catch (err) {
      if (!metrics.errorsByStatus[0]) metrics.errorsByStatus[0] = 0;
      metrics.totalLatencyMs += Date.now() - start;
      throw err;
    }
  }

  return {
    generate: async (body: any) => {
      metrics.generations++;
      return instrumentedRequest("POST", "/generations", body);
    },
    poll: (id: string) => instrumentedRequest("GET", `/generations/${id}`),
    listThemes: () => instrumentedRequest("GET", "/themes"),
    listFolders: () => instrumentedRequest("GET", "/folders"),

    // Record completion metrics
    recordCompletion: (creditsUsed: number) => {
      metrics.completions++;
      metrics.totalCredits += creditsUsed;
    },
    recordFailure: () => { metrics.failures++; },
  };
}

export function getMetrics() {
  return {
    ...metrics,
    avgLatencyMs: metrics.requests > 0
      ? Math.round(metrics.totalLatencyMs / metrics.requests) : 0,
    errorRate: metrics.requests > 0
      ? (metrics.errors / metrics.requests * 100).toFixed(2) + "%" : "0%&

                

              

                
                  
                  gamma-performance-tuning
                  View full skill →
                
                
                  'Optimize Gamma API performance and reduce latency.
                  
                      ReadWriteEdit
                    
                
                
                  Gamma Performance Tuning
Overview
Optimize Gamma API integration performance. Gamma's generate-poll-retrieve pattern means most latency is in generation time (10-60s), not API call overhead. Optimize by: reducing poll overhead, parallelizing batch operations, caching results, and choosing the right generation parameters.
Prerequisites

Working Gamma integration (see gamma-sdk-patterns)
Understanding of async patterns
Redis or in-memory cache (recommended)

Performance Characteristics

Operation
Typical Latency
Notes


POST /generations
200-500ms
Just starts the generation


GET /generations/{id} (poll)
100-300ms
Per poll request


Full generation (poll to completion)
10-60s
Depends on content + cards


GET /themes
100-200ms
Cacheable


GET /folders
100-200ms
Cacheable


Instructions
Step 1: Optimize Poll Strategy

// src/gamma/smart-poll.ts
// Adaptive polling: start fast, slow down over time

export async function smartPoll(
  gamma: GammaClient,
  generationId: string,
  opts = { maxTimeMs: 180000 }
): Promise<GenerateResult> {
  const deadline = Date.now() + opts.maxTimeMs;
  let interval = 2000; // Start at 2s

  while (Date.now() < deadline) {
    const result = await gamma.poll(generationId);

    if (result.status === "completed") return result;
    if (result.status === "failed") throw new Error("Generation failed");

    // Adaptive backoff: poll faster early, slower later
    await new Promise((r) => setTimeout(r, interval));
    interval = Math.min(interval * 1.5, 10000); // Max 10s between polls
  }

  throw new Error(`Poll timeout after ${opts.maxTimeMs}ms`);
}

Step 2: Cache Static Data

// src/gamma/cache.ts
import NodeCache from "node-cache";

const cache = new NodeCache({ stdTTL: 3600 }); // 1 hour for static data

export async function getCachedThemes(gamma: GammaClient) {
  const key = "gamma:themes";
  const cached = cache.get(key);
  if (cached) return cached;

  const themes = await gamma.listThemes();
  cache.set(key, themes);
  return themes;
}

export async function getCachedFolders(gamma: GammaClient) {
  const key = "gamma:folders";
  const cached = cache.get(key);
  if (cached) return cached;

  const folders = await gamma.listFolders();
  cache.set(key, folders);
  return folders;
}

// Cache generation results (useful for showing status)
export async function cacheGenerationResult(
  generationId: string,
  result: GenerateResult
) {
  cache.s

                

              

                
                  
                  gamma-prod-checklist
                  View full skill →
                
                
                  'Production readiness checklist for Gamma integration.
                  
                      ReadWriteEditGrep
                    
                
                
                  Gamma Production Checklist
Overview
Comprehensive checklist to ensure your Gamma integration is production-ready.
Prerequisites

Completed development and testing
Staging environment validated
Monitoring infrastructure ready

Production Checklist
1. Authentication & Security

[ ] Production API key obtained (not development key)
[ ] API key stored in secret manager (not env file)
[ ] Key rotation procedure documented and tested
[ ] Minimum required scopes configured
[ ] No secrets in source code or logs


// Production client configuration
const gamma = new GammaClient({
  apiKey: await secretManager.getSecret('GAMMA_API_KEY'),
  timeout: 30000,  # 30000: 30 seconds in ms
  retries: 3,
});

2. Error Handling

[ ] All API calls wrapped in try/catch
[ ] Exponential backoff for rate limits
[ ] Graceful degradation for API outages
[ ] User-friendly error messages
[ ] Error tracking integration (Sentry, etc.)


import * as Sentry from '@sentry/node';

try {
  await gamma.presentations.create({ ... });
} catch (err) {
  Sentry.captureException(err, {
    tags: { service: 'gamma', operation: 'create' },
  });
  throw new UserError('Unable to create presentation. Please try again.');
}

3. Performance

[ ] Client instance reused (singleton pattern)
[ ] Connection pooling enabled
[ ] Appropriate timeouts configured
[ ] Response caching where applicable
[ ] Async operations for long tasks

4. Monitoring & Logging

[ ] Request/response logging (sanitized)
[ ] Latency metrics collection
[ ] Error rate alerting
[ ] Rate limit monitoring
[ ] Health check endpoint


// Health check
app.get('/health/gamma', async (req, res) => {
  try {
    await gamma.ping();
    res.json({ status: 'healthy', service: 'gamma' });
  } catch (err) {
    res.status(503).json({ status: 'unhealthy', error: err.message });  # HTTP 503 Service Unavailable
  }
});

5. Rate Limiting

[ ] Rate limit tier confirmed with Gamma
[ ] Request queuing implemented
[ ] Backoff strategy in place
[ ] Usage monitoring alerts
[ ] Burst protection enabled

6. Data Handling

[ ] PII handling compliant with policies
[ ] Data retention policies documented
[ ] Export data properly secured
[ ] User consent for AI processing
[ ] GDPR/CCPA compliance verified

7. Disaster Recovery

[ ] Fallback behavior defined
[ ] Circuit
                
              

                
                  
                  gamma-rate-limits
                  View full skill →
                
                
                  'Understand and manage Gamma API rate limits effectively.
                  
                      ReadWriteEdit
                    
                
                
                  Gamma Rate Limits
Overview
Understand Gamma API rate limits and implement effective strategies for high-volume usage.
Prerequisites

Active Gamma API integration
Understanding of HTTP headers
Basic queuing concepts

Rate Limit Tiers

Plan
Requests/min
Presentations/day
Exports/hour


Free
10
5
10


Pro
60
50
100


Team
200
200
500


Enterprise
Custom
Custom
Custom


Instructions
Step 1: Check Rate Limit Headers

const response = await gamma.presentations.list();

// Rate limit headers
const headers = response.headers;
console.log('Limit:', headers['x-ratelimit-limit']);
console.log('Remaining:', headers['x-ratelimit-remaining']);
console.log('Reset:', new Date(headers['x-ratelimit-reset'] * 1000));  # 1000: 1 second in ms

Step 2: Implement Exponential Backoff

async function withBackoff<T>(
  fn: () => Promise<T>,
  options = { maxRetries: 5, baseDelay: 1000 }  # 1000: 1 second in ms
): Promise<T> {
  for (let attempt = 0; attempt < options.maxRetries; attempt++) {
    try {
      return await fn();
    } catch (err) {
      if (err.status !== 429 || attempt === options.maxRetries - 1) {  # HTTP 429 Too Many Requests
        throw err;
      }

      const delay = err.retryAfter
        ? err.retryAfter * 1000  # 1 second in ms
        : options.baseDelay * Math.pow(2, attempt);

      console.log(`Rate limited. Retrying in ${delay}ms...`);
      await new Promise(r => setTimeout(r, delay));
    }
  }
  throw new Error('Max retries exceeded');
}

// Usage
const result = await withBackoff(() =>
  gamma.presentations.create({ title: 'My Deck', prompt: 'AI overview' })
);

Step 3: Request Queue

class RateLimitedQueue {
  private queue: Array<() => Promise<any>> = [];
  private processing = false;
  private requestsPerMinute: number;
  private interval: number;

  constructor(requestsPerMinute = 60) {
    this.requestsPerMinute = requestsPerMinute;
    this.interval = 60000 / requestsPerMinute;  # 60000: 1 minute in ms
  }

  async add<T>(fn: () => Promise<T>): Promise<T> {
    return new Promise((resolve, reject) => {
      this.queue.push(async () => {
        try {
          resolve(await fn());
        } catch (err) {
          reject(err);
        }
      });
      this.process();
    });
  }

  private async process() {
    if (this.processing) return;
    this.processing = true;

    while (this.q

                

              

                
                  
                  gamma-reference-architecture
                  View full skill →
                
                
                  'Reference architecture for enterprise Gamma integrations.
                  
                      ReadWriteEdit
                    
                
                
                  Gamma Reference Architecture
Overview
Reference architecture patterns for building scalable, maintainable Gamma integrations.
Prerequisites

Understanding of microservices
Familiarity with cloud architecture
Knowledge of event-driven systems

Architecture Patterns
Pattern 1: Basic Integration

┌─────────────────────────────────────────────────────────┐
│                    Your Application                      │
│  ┌─────────┐    ┌─────────┐    ┌─────────┐             │
│  │   UI    │───▶│   API   │───▶│ Gamma   │             │
│  │         │    │ Server  │    │ Client  │             │
│  └─────────┘    └─────────┘    └────┬────┘             │
│                                      │                   │
└──────────────────────────────────────┼──────────────────┘
                                       │
                                       ▼
                              ┌─────────────────┐
                              │   Gamma API     │
                              └─────────────────┘

Use Case: Simple applications, prototypes, small teams.
Pattern 2: Service Layer Architecture

set -euo pipefail
┌────────────────────────────────────────────────────────────────┐
│                         Your Platform                           │
│                                                                  │
│  ┌──────────┐  ┌──────────┐  ┌──────────┐  ┌──────────┐        │
│  │  Web App │  │Mobile App│  │   CLI    │  │   API    │        │
│  └────┬─────┘  └────┬─────┘  └────┬─────┘  └────┬─────┘        │
│       │             │             │             │                │
│       └─────────────┴──────┬──────┴─────────────┘                │
│                            ▼                                     │
│                  ┌──────────────────┐                           │
│                  │ Presentation     │                           │
│                  │    Service       │                           │
│                  └────────┬─────────┘                           │
│                           │                                      │
│  ┌────────────────────────┼────────────────────────┐            │
│  │                        ▼                        │            │
│  │  ┌─────────┐  ┌─────────────┐  ┌─────────┐     │            │
│  │  │  Cache  │◀─│Gamma Client │──▶│  Queue  │     │            │
│  │  │ (Redis) │  │  Singleton  │  │ (Bull)  │     │            │
│  │  └─────────┘  └──────┬──────┘  └─────────┘     │            │
│  │                      │                          │            │
│  └──────────────────────┼──────────────────────────┘            │
│                         │                                        │
└─────────────────────────┼────────────────────────────────────────┘
                          ▼
                 ┌─────────────────┐
                 │   Gamma A

                

              

                
                  
                  gamma-sdk-patterns
                  View full skill →
                
                
                  'Reusable patterns for the Gamma REST API (no SDK exists).
                  
                      ReadWriteEdit
                    
                
                
                  Gamma API Patterns
Overview
Gamma has no published SDK — all interaction is via REST at https://public-api.gamma.app/v1.0/. This skill provides production-grade patterns for typed clients, generation helpers, polling, template workflows, and error handling.
Prerequisites

Completed gamma-install-auth setup
TypeScript project with fetch (Node.js 18+)
Understanding of the generate-poll-retrieve workflow

Instructions
Step 1: Typed Client Singleton

// lib/gamma.ts
const GAMMA_BASE = "https://public-api.gamma.app/v1.0";

interface GammaConfig {
  apiKey: string;
  baseUrl?: string;
  timeoutMs?: number;
}

// Types based on actual API responses
interface GenerateRequest {
  content: string;
  outputFormat?: "presentation" | "document" | "webpage" | "social_post";
  themeId?: string;
  exportAs?: "pdf" | "pptx" | "png";
  textMode?: "generate" | "condense" | "preserve";
  textAmount?: "brief" | "medium" | "detailed" | "extensive";
  imageOptions?: { style?: string };
  sharingOptions?: {
    workspaceAccess?: "noAccess" | "view" | "comment" | "edit" | "fullAccess";
    externalAccess?: "noAccess" | "view" | "comment" | "edit" | "fullAccess";
  };
  folderIds?: string[];
}

interface GenerateResult {
  generationId: string;
  status: "in_progress" | "completed" | "failed";
  gammaUrl?: string;
  exportUrl?: string;
  creditsUsed?: number;
}

let instance: ReturnType<typeof createGammaClient> | null = null;

export function getGamma() {
  if (!instance) {
    instance = createGammaClient({
      apiKey: process.env.GAMMA_API_KEY!,
    });
  }
  return instance;
}

export function createGammaClient(config: GammaConfig) {
  const base = config.baseUrl ?? GAMMA_BASE;
  const headers: Record<string, string> = {
    "X-API-KEY": config.apiKey,
    "Content-Type": "application/json",
  };

  async function request<T>(method: string, path: string, body?: unknown): Promise<T> {
    const controller = new AbortController();
    const timeout = setTimeout(() => controller.abort(), config.timeoutMs ?? 30000);
    try {
      const res = await fetch(`${base}${path}`, {
        method,
        headers,
        body: body ? JSON.stringify(body) : undefined,
        signal: controller.signal,
      });
      if (!res.ok) {
        const text = await res.text();
        throw new GammaApiError(res.status, text, path);
      }
      return res.json() as T;
    } finally {
      clearTimeout(timeout);
    }
  }

  return {
    generate: (body: GenerateRequest) =>
      request&l

                

              

                
                  
                  gamma-security-basics
                  View full skill →
                
                
                  'Implement security best practices for Gamma integration.
                  
                      ReadWriteEditGrep
                    
                
                
                  Gamma Security Basics
Overview
Security best practices for Gamma API integration to protect credentials and data.
Prerequisites

Active Gamma integration
Environment variable support
Understanding of secret management

Instructions
Step 1: Secure API Key Storage

// NEVER do this
const gamma = new GammaClient({
  apiKey: 'gamma_live_abc123...', // Hardcoded - BAD!
});

// DO this instead
const gamma = new GammaClient({
  apiKey: process.env.GAMMA_API_KEY,
});

Environment Setup:

# .env (add to .gitignore!)
GAMMA_API_KEY=gamma_live_abc123...

# Load in application
import 'dotenv/config';

Step 2: Key Rotation Strategy

// Support multiple keys for rotation
const gamma = new GammaClient({
  apiKey: process.env.GAMMA_API_KEY_PRIMARY
    || process.env.GAMMA_API_KEY_SECONDARY,
});

// Rotation script
async function rotateApiKey() {
  // 1. Generate new key in Gamma dashboard
  // 2. Update GAMMA_API_KEY_SECONDARY
  // 3. Deploy and verify
  // 4. Swap PRIMARY and SECONDARY
  // 5. Revoke old key
}

Step 3: Request Signing (if supported)

import crypto from 'crypto';

function signRequest(payload: object, secret: string): string {
  const timestamp = Date.now().toString();
  const message = timestamp + JSON.stringify(payload);

  return crypto
    .createHmac('sha256', secret)
    .update(message)
    .digest('hex');
}

// Usage with webhook verification
function verifyWebhook(body: string, signature: string, secret: string): boolean {
  const expected = crypto
    .createHmac('sha256', secret)
    .update(body)
    .digest('hex');

  return crypto.timingSafeEqual(
    Buffer.from(signature),
    Buffer.from(expected)
  );
}

Step 4: Access Control Patterns

// Scoped API keys (if supported)
const readOnlyGamma = new GammaClient({
  apiKey: process.env.GAMMA_API_KEY_READONLY,
  scopes: ['presentations:read', 'exports:read'],
});

const fullAccessGamma = new GammaClient({
  apiKey: process.env.GAMMA_API_KEY_FULL,
});

// Permission check before operations
async function createPresentation(user: User, data: object) {
  if (!user.permissions.includes('gamma:create')) {
    throw new Error('Insufficient permissions');
  }
  return fullAccessGamma.presentations.create(data);
}

Step 5: Audit Logging

import { GammaClient } from '@gamma/sdk';

function createAuditedClient(userId: string) {
  return new GammaClient({
    apiKey: process.env.GAMMA_API_KEY,
    interceptors: {
      request: (config) => {
        console.log(JSON.stringify({
          timesta

                

              

                
                  
                  gamma-upgrade-migration
                  View full skill →
                
                
                  'Upgrade Gamma SDK versions and migrate between API versions.
                  
                      ReadWriteEditBash(npm:*)Bash(pip:*)Grep
                    
                
                
                  Gamma Upgrade & Migration
Current State
!npm list 2>/dev/null | head -20
!pip freeze 2>/dev/null | head -20
Overview
Guide for upgrading Gamma SDK versions and migrating between API versions safely.
Prerequisites

Existing Gamma integration
Version control (git)
Test environment available

Instructions
Step 1: Check Current Version

set -euo pipefail
# Node.js
npm list @gamma/sdk

# Python
pip show gamma-sdk

# Check for available updates
npm outdated @gamma/sdk

Step 2: Review Changelog

set -euo pipefail
# View changelog
npm info @gamma/sdk changelog

# Or visit
# https://gamma.app/docs/changelog

Step 3: Upgrade SDK

set -euo pipefail
# Create upgrade branch
git checkout -b feat/gamma-sdk-upgrade

# Node.js - upgrade to latest
npm install @gamma/sdk@latest

# Python - upgrade to latest
pip install --upgrade gamma-sdk

# Or specific version
npm install @gamma/sdk@2.0.0

Step 4: Handle Breaking Changes
Common Migration Patterns:

// v1.x -> v2.x: Client initialization change
// Before (v1)
import Gamma from '@gamma/sdk';
const gamma = new Gamma(apiKey);

// After (v2)
import { GammaClient } from '@gamma/sdk';
const gamma = new GammaClient({ apiKey });


// v1.x -> v2.x: Response format change
// Before (v1)
const result = await gamma.createPresentation({ title: 'Test' });
console.log(result.id);

// After (v2)
const result = await gamma.presentations.create({ title: 'Test' });
console.log(result.data.id);


// v1.x -> v2.x: Error handling change
// Before (v1)
try {
  await gamma.create({ ... });
} catch (e) {
  if (e.code === 'RATE_LIMIT') { ... }
}

// After (v2)
import { RateLimitError } from '@gamma/sdk';
try {
  await gamma.presentations.create({ ... });
} catch (e) {
  if (e instanceof RateLimitError) { ... }
}

Step 5: Update Type Definitions

// Check for type changes
// tsconfig.json - ensure strict mode catches issues
{
  "compilerOptions": {
    "strict": true,
    "noImplicitAny": true
  }
}

// Run type check
npx tsc --noEmit

Step 6: Test Thoroughly

set -euo pipefail
# Run unit tests
npm test

# Run integration tests
npm run test:integration

# Manual smoke test
node -e "
const { GammaClient } = require('@gamma/sdk');
const g = new GammaClient({ apiKey: process.env.GAMMA_API_KEY });
g.ping().then(() => console.log('OK')).catch(console.error);
"

Step 7: Deprecation 
                
              

                
                  
                  gamma-webhooks-events
                  View full skill →
                
                
                  'Handle Gamma webhooks and events for real-time updates.
                  
                      ReadWriteEdit
                    
                
                
                  Gamma Webhooks & Events
Overview
Gamma's public API (v1.0) is generation-focused and does not expose a traditional webhook system at time of writing. Instead, use the poll-based pattern (GET /v1.0/generations/{id}) to detect completion. For event-driven architectures, wrap polling in a background worker that emits application-level events when generations complete or fail.
Prerequisites

Completed gamma-sdk-patterns setup
Event bus or message queue (Bull, RabbitMQ, or EventEmitter)
Understanding of the generate-poll-retrieve pattern

Gamma Event Model (Application-Level)
Since Gamma does not push events, you create them by polling:

Synthetic Event
Trigger Condition
Use Case


generation.started
POST /generations returns generationId
Log, notify user


generation.completed
Poll returns status: "completed"
Download export, update DB


generation.failed
Poll returns status: "failed"
Alert, retry, notify user


generation.timeout
Poll exceeds max duration
Alert, escalate


Instructions
Step 1: Event Emitter Pattern

// src/gamma/events.ts
import { EventEmitter } from "events";
import { createGammaClient } from "./client";

export const gammaEvents = new EventEmitter();

export interface GenerationEvent {
  generationId: string;
  status: "started" | "completed" | "failed" | "timeout";
  gammaUrl?: string;
  exportUrl?: string;
  creditsUsed?: number;
  error?: string;
}

export async function generateWithEvents(
  content: string,
  options: { outputFormat?: string; exportAs?: string; themeId?: string } = {}
): Promise<GenerationEvent> {
  const gamma = createGammaClient({ apiKey: process.env.GAMMA_API_KEY! });

  // Start generation
  const { generationId } = await gamma.generate({
    content,
    outputFormat: options.outputFormat ?? "presentation",
    exportAs: options.exportAs,
    themeId: options.themeId,
  });

  gammaEvents.emit("generation", {
    generationId,
    status: "started",
  } as GenerationEvent);

  // Poll for completion
  const deadline = Date.now() + 180000; // 3 minute timeout
  while (Date.now() < deadline) {
    const result = await gamma.poll(generationId);

    if (result.status === "completed") {
      const event: GenerationEvent = {
        generationId,
        status: "completed",
        gammaUrl: result.gammaUrl,
        exportUrl: result.exportUrl,
        creditsUsed: result.creditsUsed,



      
      
          How It Works
          Skills trigger automatically when you discuss Gamma topics:

"Help me set up Gamma API" triggers gamma-install-auth
"Generate a presentation with Gamma" triggers gamma-core-workflow-a
"Debug this Gamma error" triggers gamma-common-errors
"Deploy my Gamma integration" triggers gamma-deploy-integration
"Migrate from PowerPoint to Gamma" triggers gamma-migration-deep-dive

        

      
      

      
      

      
      
  Ready to use gamma-pack?
  
    
    
  




      
      
          Related Plugins
          
            
  supabase-pack
  Complete Supabase integration skill pack with 30 skills covering authentication, database, storage, realtime, edge functions, and production operations. Flagship+ tier vendor pack.
  /plugin install supabase-pack@claude-code-plugins-plus
  

  vercel-pack
  Complete Vercel integration skill pack with 30 skills covering deployments, edge functions, preview environments, performance optimization, and production operations. Flagship+ tier vendor pack.
  /plugin install vercel-pack@claude-code-plugins-plus
  

  clay-pack
  Complete Clay integration skill pack with 30 skills covering data enrichment, waterfall workflows, AI agents, and GTM automation. Flagship+ tier vendor pack.
  /plugin install clay-pack@claude-code-plugins-plus
  

  cursor-pack
  Complete Cursor integration skill pack with 30 skills covering AI code editing, composer workflows, codebase indexing, and productivity features. Flagship+ tier vendor pack.
  /plugin install cursor-pack@claude-code-plugins-plus
  

  exa-pack
  Complete Exa integration skill pack with 30 skills covering neural search, semantic retrieval, web search API, and AI-powered discovery. Flagship+ tier vendor pack.
  /plugin install exa-pack@claude-code-plugins-plus
  

  firecrawl-pack
  Complete Firecrawl integration skill pack with 30 skills covering web scraping, crawling, markdown conversion, and LLM-ready data extraction. Flagship+ tier vendor pack.
  /plugin install firecrawl-pack@claude-code-plugins-plus
  

          
        

      
      
          Tags
          
            gammapresentationsdocumentsai-generationtemplatesslidesvisual-content

Parameter	Type	Options	Default
`content`	string	Your text/prompt	Required
`outputFormat`	string	`presentation`, `document`, `webpage`, `social_post`	`presentation`
`textMode`	string	`generate`, `condense`, `preserve`	`generate`
`textAmount`	string	`brief`, `medium`, `detailed`, `extensive`	`medium`
`themeId`	string	From `GET /v1.0/themes`	Workspace default
`imageOptions.style`	string	Free text (e.g., `"photorealistic"`, `"watercolor illustration"`)	AI default
`exportAs`	string	`pdf`, `pptx`, `png`	None (no auto-export)
`sharingOptions`	object	`workspaceAccess`, `externalAccess`	Workspace defaults
`folderIds`	string[]	From `GET /v1.0/folders`	Root folder

Tier	Credits per Image	Quality Level
Standard	2-15	Good for internal/draft presentations
Advanced	20-33	Higher quality, more detail
Premium	34-75	Best quality images
Ultra	30-125	Highest fidelity, photorealistic

Feature	Pro	Ultra	Teams	Business
Monthly credits	Included	More credits	Team pool	Custom
API access	Yes	Yes	Yes	Yes
Max cards	Standard	Up to 75	Standard	Custom
Ad-hoc credit purchase	Yes	Yes	Yes	Yes
Auto-recharge	Yes	Yes	Yes	Yes

Data Type	Classification	Where Stored	Retention
API key	Secret	Your env vars	Active use only
Content/prompts	May contain PII	Gamma servers (during generation)	Gamma's policy
Generated gammas	User data	Gamma workspace	User-controlled
Export files (PDF/PPTX)	User data	Temporary URLs	Download promptly, URLs expire
User prompts in logs	PII risk	Your infrastructure	Your policy (sanitize!)
Credit usage	Billing data	Gamma	Per Gamma ToS

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

Approach	When to Use	Effort
Content extraction + regeneration	Lots of text-heavy presentations	Medium
Import via Gamma UI	One-off migration of key decks	Low
Template recreation	Repeatable presentation formats	Medium
Parallel operation	Gradual transition over time	Low

Operation	Typical Latency	Notes
POST `/generations`	200-500ms	Just starts the generation
GET `/generations/{id}` (poll)	100-300ms	Per poll request
Full generation (poll to completion)	10-60s	Depends on content + cards
GET `/themes`	100-200ms	Cacheable
GET `/folders`	100-200ms	Cacheable

Plan	Requests/min	Presentations/day	Exports/hour
Free	10	5	10
Pro	60	50	100
Team	200	200	500
Enterprise	Custom	Custom	Custom

Synthetic Event	Trigger Condition	Use Case
`generation.started`	POST `/generations` returns `generationId`	Log, notify user
`generation.completed`	Poll returns `status: "completed"`	Download export, update DB
`generation.failed`	Poll returns `status: "failed"`	Alert, retry, notify user
`generation.timeout`	Poll exceeds max duration	Alert, escalate