GA

gamma-common-errors

A diagnostic reference for troubleshooting Gamma API errors, including status codes for auth, rate limits, and request failures.

Install

mkdir -p .claude/skills/gamma-common-errors && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6903" && unzip -o skill.zip -d .claude/skills/gamma-common-errors && rm skill.zip

Installs to .claude/skills/gamma-common-errors

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Debug and resolve common Gamma API errors.
42 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Verify API key validity
  • Implement exponential backoff for rate limits
  • Simplify prompts for generation errors
  • Increase client timeout settings
  • Check API status and service health
  • Handle typed SDK exceptions for Gamma API

How it works

The skill categorizes Gamma API errors by HTTP status code, such as 401 for authentication or 429 for rate limits. It provides specific solutions for each error type, including code examples for retries and client configuration.

Inputs & outputs

You give it
Gamma API error messages and HTTP status codes
You get back
Diagnosis of error class, root cause, and concrete fix

When to use gamma-common-errors

  • Troubleshoot authentication failures
  • Implement exponential backoff for rate limits
  • Debug API request structures
  • Verify environment variable configurations

About this skill

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:

  1. Verify API key in Gamma dashboard
  2. Check environment variable is set: echo $GAMMA_API_KEY
  3. Ensure key hasn't been rotated
  4. Check for trailing whitespace in key

Rate Limit Errors (429)

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

Solutions:

  1. Implement exponential backoff
  2. Check rate limit headers: X-RateLimit-Remaining
  3. Upgrade plan for higher limits
  4. 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:

  1. Simplify prompt or reduce slide count
  2. Remove special characters from content
  3. Check content length limits
  4. Try different style setting

Timeout Errors

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

Solutions:

  1. Increase client timeout setting
  2. Use async job pattern for large presentations
  3. Check network connectivity
  4. 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_failed",
  "message": "Unable to export presentation",
  "format": "pdf"
}

Solutions:

  1. Verify presentation exists and is complete
  2. Check supported export formats
  3. Ensure no pending generation jobs
  4. Try exporting with lower quality setting

Debugging Tools

Enable Debug Logging

const gamma = new GammaClient({
  apiKey: process.env.GAMMA_API_KEY,
  debug: true, // Logs all requests/responses
});

Check API Status

const status = await gamma.status();
console.log('API Status:', status.healthy ? 'OK' : 'Issues');
console.log('Services:', status.services);

Error Handling Pattern

import { GammaError, RateLimitError, AuthError } from '@gamma/sdk';

try {
  const result = await gamma.presentations.create({ ... });
} catch (err) {
  if (err instanceof AuthError) {
    console.error('Check your API key');
  } else if (err instanceof RateLimitError) {
    console.error(`Retry after ${err.retryAfter}s`);
  } else if (err instanceof GammaError) {
    console.error('API Error:', err.message);
  } else {
    throw err;
  }
}

Resources

Next Steps

Proceed to gamma-debug-bundle for comprehensive debugging tools.

When not to use it

  • When debugging non-Gamma API errors
  • When the issue is not related to API communication
  • When Gamma integration is not active

Prerequisites

Active Gamma integrationAccess to logs and error messagesUnderstanding of HTTP status codes

Limitations

  • Cannot remove seat if user has admin role
  • Storage limit warning if too many transcripts
  • API daily limit hit on Free/Pro plans

How it compares

This skill offers a structured approach to debugging Gamma API errors with specific solutions, unlike general API troubleshooting.

Compared to similar skills

gamma-common-errors side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
gamma-common-errors (this skill)124dReviewIntermediate
n8n-expression-syntax64moNo flagsBeginner
claude-in-chrome-troubleshooting22moReviewIntermediate
openrouter-common-errors324dCautionIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

You might also like

n8n-expression-syntax

czlonkowski

Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.

6111

claude-in-chrome-troubleshooting

trailofbits

Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.

211

openrouter-common-errors

jeremylongshore

Execute diagnose and fix common OpenRouter API errors. Use when troubleshooting failed requests. Trigger with phrases like 'openrouter error', 'openrouter not working', 'openrouter 401', 'openrouter 429', 'fix openrouter'.

39

linear-common-errors

jeremylongshore

Diagnose and fix common Linear API errors. Use when encountering Linear API errors, debugging integration issues, or troubleshooting authentication problems. Trigger with phrases like "linear error", "linear API error", "debug linear", "linear not working", "linear authentication error".

16

groq-common-errors

jeremylongshore

Diagnose and fix Groq common errors and exceptions. Use when encountering Groq errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "groq error", "fix groq", "groq not working", "debug groq".

12

linear-debug-bundle

jeremylongshore

Comprehensive debugging toolkit for Linear integrations. Use when setting up logging, tracing API calls, or building debug utilities for Linear. Trigger with phrases like "debug linear integration", "linear logging", "trace linear API", "linear debugging tools", "linear troubleshooting".

12

Search skills

Search the agent skills registry