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.zipInstalls 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.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
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:
- Verify API key in Gamma dashboard
- Check environment variable is set:
echo $GAMMA_API_KEY - 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_failed",
"message": "Unable to export presentation",
"format": "pdf"
}
Solutions:
- Verify presentation exists and is complete
- Check supported export formats
- Ensure no pending generation jobs
- 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
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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gamma-common-errors (this skill) | 1 | 24d | Review | Intermediate |
| n8n-expression-syntax | 6 | 4mo | No flags | Beginner |
| claude-in-chrome-troubleshooting | 2 | 2mo | Review | Intermediate |
| openrouter-common-errors | 3 | 24d | Caution | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →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.
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.
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'.
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".
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".
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".