gamma-debug-bundle
A collection of scripts and diagnostics to troubleshoot and trace Gamma API integration problems.
Install
mkdir -p .claude/skills/gamma-debug-bundle && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5340" && unzip -o skill.zip -d .claude/skills/gamma-debug-bundle && rm skill.zipInstalls to .claude/skills/gamma-debug-bundle
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.
Comprehensive debugging toolkit for Gamma integration issues.Key capabilities
- →Run connectivity tests against Gamma endpoints
- →Verify API key authentication status
- →Trace API request latency and responses
- →Generate diagnostic reports for support tickets
- →Inspect workspace themes and folder access
How it works
The skill provides a suite of diagnostic scripts and curl commands to verify connectivity, authentication, and API health by interacting with Gamma's REST endpoints.
Inputs & outputs
When to use gamma-debug-bundle
- →Running connectivity tests against Gamma endpoints
- →Verifying API key authentication
- →Tracing failed API requests
- →Generating diagnostic logs for support requests
About gamma-debug-bundle
Offers a suite of tools including connectivity testers, authentication verifiers, and logging patterns to help diagnose issues within Gamma API workflows.
Comprehensive debugging toolkit for Gamma integration issues. Use when you need detailed diagnostics, request tracing, or systematic debugging of Gamma API problems. Trigger with phrases like "gamma debug bundle", "gamma diagnostics", "gamma trace", "gamma inspect", "gamma detailed logs".
When not to use it
- →Running diagnostic generations in production without credit awareness
- →Ignoring 429 rate limit errors
Prerequisites
Limitations
- →Diagnostic generation consumes credits
- →Requires Node.js 18+ or Python 3.10+
How it compares
This provides a systematic, automated diagnostic path for integration issues rather than manual trial-and-error debugging.
Compared to similar skills
gamma-debug-bundle side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gamma-debug-bundle (this skill) | 1 | 4mo | Caution | Intermediate |
| n8n-expression-syntax | 6 | 7mo | No flags | Beginner |
| claude-in-chrome-troubleshooting | 2 | 5mo | Review | Intermediate |
| openrouter-common-errors | 3 | 4mo | 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".
gamma-common-errors
jeremylongshore
Debug and resolve common Gamma API errors. Use when encountering authentication failures, rate limits, generation errors, or unexpected API responses. Trigger with phrases like "gamma error", "gamma not working", "gamma API error", "gamma debug", "gamma troubleshoot".
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".