gamma-common-errors
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".
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/gamma-pack/skills/gamma-common-errors/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with strong completeness and distinctiveness. It excels at providing explicit trigger guidance and carving out a clear niche around Gamma API errors. The main weakness is that the capability description could be more specific about what concrete debugging/resolution actions the skill performs beyond the general 'debug and resolve'.
Suggestions
Add more specific concrete actions beyond 'debug and resolve', such as 'diagnose error codes, suggest authentication fixes, recommend retry strategies for rate limits, parse error response bodies'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gamma API errors) and some actions (debug and resolve), and lists categories of errors (authentication failures, rate limits, generation errors, unexpected API responses), but doesn't describe specific concrete resolution actions beyond 'debug and resolve'. | 2 / 3 |
Completeness | Clearly answers both 'what' (debug and resolve common Gamma API errors including authentication failures, rate limits, generation errors, unexpected API responses) and 'when' (explicit 'Use when' clause and 'Trigger with phrases' section providing clear activation guidance). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that users would actually say: 'gamma error', 'gamma not working', 'gamma API error', 'gamma debug', 'gamma troubleshoot'. Also includes domain-specific terms like 'authentication failures', 'rate limits', and 'generation errors'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche — specifically targets Gamma API errors. The trigger terms are all Gamma-specific, making it very unlikely to conflict with other API debugging skills or general error-handling skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid error reference guide with good actionable code examples covering the main Gamma API error categories. Its main weaknesses are the lack of a structured debugging workflow with explicit validation checkpoints and some verbosity in areas like prerequisites. The progressive disclosure could be improved by splitting detailed error references into a separate file and keeping SKILL.md as a concise overview.
Suggestions
Add an explicit debugging workflow at the top (e.g., '1. Check API status → 2. Verify auth → 3. Inspect error response → 4. Apply fix → 5. Verify resolution') with validation checkpoints.
Remove the Prerequisites section — Claude already understands HTTP status codes and doesn't need to be told to have access to logs.
Fix the syntax error in the retry function: `# 1000: 1 second in ms` uses Python comment syntax inside TypeScript code — use `//` instead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements like the Prerequisites section (Claude knows what HTTP status codes are) and some redundant inline comments. The error examples are well-structured but could be slightly tighter. | 2 / 3 |
Actionability | Provides concrete, executable TypeScript code for each error scenario including retry logic, error handling patterns, debug logging setup, and status checking. The solutions are specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | Each error type has clear solutions listed in order, but there's no explicit debugging workflow that sequences steps (e.g., 'first check X, then try Y, validate with Z'). The error handling pattern at the end is good but lacks a feedback loop for iterative debugging. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections per error type, and references external resources and a 'gamma-debug-bundle'. However, the inline content is quite long and some error categories could be split into separate reference files. The reference to 'gamma-debug-bundle' at the end is vague with no clear path. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
a04d1a2
- 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.