Why Use This This skill provides specialized capabilities for jeremylongshore's codebase.
Use Cases Developing new features in the jeremylongshore repository Refactoring existing code to follow jeremylongshore standards Understanding and working with jeremylongshore's codebase structure
Install Guide 2 steps 1 2 Install inside Ananke
Click Install Skill, paste the link below, then press Install.
https://github.com/jeremylongshore/claude-code-plugins-plus-skills/tree/main/plugins/saas-packs/gamma-pack/skills/gamma-debug-bundle Skill Snapshot Auto scan of skill assets. Informational only.
Valid SKILL.md Checks against SKILL.md specification
Source & Community
Updated At Mar 11, 2026, 05:33 AM
Skill Stats
SKILL.md 77 Lines
Total Files 2
Total Size 2.6 KB
License MIT
---
name: gamma-debug-bundle
description: |
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".
allowed-tools: Read, Write, Edit, Bash(node:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Gamma Debug Bundle
## Contents
- [Overview](#overview)
- [Prerequisites](#prerequisites)
- [Instructions](#instructions)
- [Output](#output)
- [Error Handling](#error-handling)
- [Examples](#examples)
- [Resources](#resources)
## Overview
Comprehensive debugging toolkit for systematic troubleshooting of Gamma integration issues including request tracing, environment checks, and exportable debug bundles.
## Prerequisites
- Active Gamma integration with issues
- Node.js 18+ for debug tools
- Access to application logs
## Instructions
### Step 1: Create Debug Client
Wrap GammaClient with request/response/error interceptors that log method, path, duration, status, and full payloads.
### Step 2: Run Diagnostic Script
Sequential tests: authentication (ping), API access (list presentations), generation (dry-run create), and rate limit status check.
### Step 3: Check Environment
Verify GAMMA_API_KEY is set, NODE_ENV is correct, and Node.js version is compatible.
### Step 4: Export Debug Bundle
Package environment info, request logs, and config into a JSON file for sharing with support.
See [detailed implementation](${CLAUDE_SKILL_DIR}/references/implementation.md) for debug client with interceptors, diagnostic script, environment checker, and bundle export code.
## Output
- Debug client with full request tracing
- Diagnostic report with pass/fail for each subsystem
- Environment verification report
- Exportable JSON debug bundle
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| Auth test fails | Invalid API key | Verify GAMMA_API_KEY env var |
| List returns empty | No presentations | Create test presentation first |
| Generation fails | Rate limit or quota | Check rate limit status |
| Timeout errors | Network issues | Check connectivity to gamma.app |
## Examples
### Quick Diagnostic
```bash
npx ts-node debug/diagnose.ts
# Output: 4 tests with pass/fail and request log summary
```
## Resources
- [Gamma Debug Guide](https://gamma.app/docs/debugging)
- [Gamma Support Portal](https://gamma.app/support)
## Next Steps
Proceed to `gamma-rate-limits` for rate limit management.