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".
80
77%
Does it follow best practices?
Impact
Pending
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 that excels in completeness and distinctiveness by clearly specifying both what it does and when to use it, with Gamma-specific trigger terms. Its main weakness is that the capability description could be more specific about the concrete debugging actions performed (e.g., checking API keys, handling retry logic, parsing error codes) rather than just listing error categories.
Suggestions
Add more specific concrete actions beyond 'debug and resolve', such as 'check API key validity, implement retry logic for rate limits, parse error response codes, validate request payloads'.
| 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 concrete, executable code examples for each common Gamma API error type. Its main weaknesses are the lack of an overarching debugging workflow that guides Claude through a systematic diagnosis process, and the somewhat monolithic structure that could benefit from splitting detailed error references into a separate file. The Prerequisites section and some inline comments add unnecessary tokens.
Suggestions
Add a top-level debugging workflow that sequences the diagnosis steps (e.g., '1. Check API status → 2. Verify auth → 3. Inspect error response → 4. Apply fix → 5. Verify resolution') to improve workflow clarity.
Remove the Prerequisites section — Claude already understands HTTP status codes and doesn't need to be told to have access to logs.
Consider moving the detailed error reference into a separate ERRORS_REFERENCE.md file and keeping only a summary table with links in the main skill file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elements like the Prerequisites section (Claude knows what HTTP status codes are) and some comments that add little value. The error JSON examples are useful but slightly verbose in aggregate. | 2 / 3 |
Actionability | Provides concrete, executable TypeScript code for each error scenario including retry logic, client configuration, debug logging, and a comprehensive error handling pattern with specific error classes. Solutions are specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | Each error type has clear solution steps, but there's no overall debugging workflow that sequences the diagnosis process (e.g., 'first check status, then check auth, then check rate limits'). The error handling pattern at the end is good but lacks a validate-fix-retry feedback loop for the debugging process itself. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers for each error type, but it's somewhat monolithic — the full error reference could be split into a separate file with just a summary here. The reference to 'gamma-debug-bundle' at the end is good but the main content is quite long for an overview skill. | 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
70e9fa4
- 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.