gamma-rate-limits
Understand and manage Gamma API rate limits effectively. Use when hitting rate limits, optimizing API usage, or implementing request queuing systems. Trigger with phrases like "gamma rate limit", "gamma quota", "gamma 429", "gamma throttle", "gamma request limits".
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-rate-limits/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 solid skill description with excellent trigger terms and completeness. Its main weakness is that the capability descriptions could be more concrete—listing specific actions like parsing 429 headers, implementing backoff strategies, or configuring retry logic would strengthen the specificity. Overall it performs well for skill selection purposes due to its clear niche and explicit trigger guidance.
Suggestions
Replace vague phrases like 'understand and manage' with specific concrete actions such as 'parse 429 response headers, implement exponential backoff, configure retry logic, and calculate quota usage'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Gamma API rate limits) and mentions some actions like 'optimizing API usage' and 'implementing request queuing systems', but these are somewhat vague and not fully concrete. It doesn't list specific actions like 'parse 429 response headers', 'calculate retry-after delays', or 'implement exponential backoff'. | 2 / 3 |
Completeness | Clearly answers both 'what' (understand and manage Gamma API rate limits, optimize API usage, implement request queuing) and 'when' (hitting rate limits, optimizing API usage, implementing request queuing) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms: 'gamma rate limit', 'gamma quota', 'gamma 429', 'gamma throttle', 'gamma request limits'. These cover common variations a user would naturally say when encountering rate limiting issues with the Gamma API. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Gamma API rate limits, which is a clear niche. The trigger terms all include 'gamma' as a qualifier, making it very unlikely to conflict with generic rate limiting skills or other API-specific 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.
The skill provides solid, actionable TypeScript code for handling Gamma API rate limits with good coverage of common patterns (backoff, queuing, monitoring). However, it's somewhat verbose with repeated inline comments explaining trivial constants, includes unnecessary prerequisite/output sections, and lacks validation checkpoints in its workflow. The content would benefit from being split into a concise overview with detailed implementations in separate bundle files.
Suggestions
Remove repeated inline comments like '# 1000: 1 second in ms' and the Prerequisites section—Claude already understands these concepts.
Add explicit validation checkpoints, e.g., 'Test backoff by intentionally triggering a 429 and verifying retry behavior' or 'Log queue depth to confirm requests are draining at expected rate'.
Extract the full RateLimitedQueue class and withBackoff implementation into separate bundle files (e.g., rate-limit-queue.ts, backoff.ts) and reference them from the SKILL.md overview.
Remove the generic 'Output' section which lists vague outcomes rather than concrete expected results.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary elements like the 'Prerequisites' section (Claude knows HTTP headers and queuing concepts), inline comments explaining basic constants like '1000: 1 second in ms' repeatedly, and the 'Output' section which is vague filler. The rate limit tiers table and code examples are useful but the overall content could be tightened. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code for each step: checking headers, exponential backoff with retry logic, a complete rate-limited queue class, and usage monitoring. The code is copy-paste ready with usage examples included. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (check headers → implement backoff → queue → monitor), but there are no explicit validation checkpoints or feedback loops. For rate limiting—which involves retry logic and potential failure cascades—there should be explicit verification steps (e.g., 'verify backoff is working by checking logs' or 'validate queue draining correctly'). | 2 / 3 |
Progressive Disclosure | The content is somewhat monolithic—the full queue implementation and backoff logic are inlined when they could be referenced as separate files. The error handling table at the end provides good summary structure, but the skill is over 100 lines with no bundle files to offload detailed implementations to. | 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
3a2d27d
- 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.