gamma-common-errors
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill gamma-common-errorsDebug 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
88%This is a strong error reference guide with excellent actionability and conciseness. The code examples are executable and the error categories are well-organized. The main weakness is the lack of a structured debugging workflow that guides users through a diagnostic sequence with validation checkpoints.
Suggestions
Add a 'Debugging Sequence' section at the top with ordered steps: 1. Check API status, 2. Verify authentication, 3. Review error response, 4. Apply specific fix, 5. Verify resolution
Include validation commands after each solution category to confirm the fix worked (e.g., 'Verify fix: run `gamma.status()` and confirm healthy: true')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient - jumps directly to error codes and solutions without explaining what APIs are or how HTTP works. Every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable TypeScript code for retry logic, error handling patterns, and client configuration. Solutions are specific and copy-paste ready with concrete commands like `echo $GAMMA_API_KEY`. | 3 / 3 |
Workflow Clarity | Solutions are listed but lack explicit validation checkpoints. For debugging workflows, there's no clear sequence like 'check X first, then Y, verify with Z'. The error handling pattern is good but debugging steps could benefit from a clearer diagnostic sequence. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections for each error type. References to external resources (status page, docs, support) and next steps (gamma-debug-bundle) are clearly signaled and one level deep. | 3 / 3 |
Total | 11 / 12 Passed |
Activation
90%This is a well-structured skill description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is that the 'what' portion could be more specific about the actual debugging actions performed (e.g., 'check API keys', 'analyze error codes', 'suggest retry strategies') rather than just listing error categories.
Suggestions
Enhance specificity by listing concrete debugging actions like 'analyze error codes, verify API key configuration, suggest retry strategies, diagnose rate limit issues'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gamma API errors) and lists categories of errors (authentication failures, rate limits, generation errors, unexpected API responses), but doesn't describe concrete debugging actions or resolution steps. | 2 / 3 |
Completeness | Clearly answers both what (debug and resolve Gamma API errors) and when (encountering authentication failures, rate limits, etc.) with explicit trigger phrases provided in a dedicated section. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'gamma error', 'gamma not working', 'gamma API error', 'gamma debug', 'gamma troubleshoot' - these are realistic phrases users would naturally use when encountering issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Gamma' as a specific product identifier and clear error-handling focus. The explicit trigger phrases with 'gamma' prefix make it unlikely to conflict with other debugging or API skills. | 3 / 3 |
Total | 11 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.