deepgram-rate-limits
Implement Deepgram rate limiting and backoff strategies. Use when handling API quotas, implementing request throttling, or dealing with 429 rate limit errors. Trigger: "deepgram rate limit", "deepgram throttling", "429 error deepgram", "deepgram quota", "deepgram backoff", "deepgram concurrency".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 trigger terms and clear 'what/when' guidance. Its main weakness is that the capability description could be more specific about the concrete actions involved (e.g., exponential backoff configuration, retry logic, concurrency limits). Overall it performs well for skill selection purposes due to its explicit trigger list and narrow domain focus.
Suggestions
Expand the capability description with more concrete actions, e.g., 'configure exponential backoff delays, set max concurrent requests, implement retry logic for failed requests, manage request queues'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Deepgram rate limiting) and some actions (rate limiting, backoff strategies), but doesn't list multiple concrete implementation actions like 'configure retry delays, set max concurrent requests, implement exponential backoff, handle 429 responses'. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement Deepgram rate limiting and backoff strategies) and 'when' (handling API quotas, request throttling, 429 rate limit errors) with an explicit 'Use when' clause and explicit trigger terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'deepgram rate limit', '429 error deepgram', 'deepgram throttling', 'deepgram quota', 'deepgram backoff', and 'deepgram concurrency' — these are terms users would naturally use when encountering these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'Deepgram' with 'rate limiting' and '429 errors' creates a very specific niche that is unlikely to conflict with other skills, even general rate-limiting or other API-related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with executable TypeScript code and a clear progressive workflow from basic rate limiting to a full resilient client pattern. The main weakness is length — the circuit breaker and combined client patterns are somewhat verbose for a SKILL.md and could be split into referenced files. The Deepgram-specific concurrency model explanation and plan limits table add genuine value.
Suggestions
Consider moving the circuit breaker (Step 3) and combined client (Step 4) implementations into a separate PATTERNS.md file, keeping only the concurrency queue and retry logic inline with references to the advanced patterns.
The circuit breaker is a generic pattern — trim it to show only the Deepgram-specific integration points and link to a reference for the full implementation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly efficient and provides Deepgram-specific knowledge Claude wouldn't have (concurrency model, plan limits), but the code examples are quite lengthy. The circuit breaker implementation is a well-known pattern that could be more concise, and the combined client in Step 4 adds bulk without much new information. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports, concrete API calls using the Deepgram SDK, and production-ready usage patterns. The examples are copy-paste ready with real method names and configuration values. | 3 / 3 |
Workflow Clarity | The 5-step progression is logically sequenced from basic concurrency control through retry logic, circuit breaker, combined pattern, and monitoring. Each step builds on the previous, and the circuit breaker provides explicit validation/feedback loops (CLOSED -> OPEN -> HALF_OPEN state transitions with recovery). The error handling table provides clear resolution steps. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful error handling table, but it's quite long (~200 lines of code) and could benefit from splitting the circuit breaker and combined client into separate reference files. The Resources section provides good external links, but the inline content is heavy for a SKILL.md overview. | 2 / 3 |
Total | 10 / 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.