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 it performs (e.g., exponential backoff configuration, retry logic, concurrency limits). The explicit trigger term list and 'Use when' clause make it highly effective for skill selection.
Suggestions
Expand the capability description with more concrete actions, e.g., 'Implements exponential backoff, configures retry logic, sets concurrency limits, and handles 429 responses for Deepgram API calls.'
| 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/backoff creates a very specific niche that is unlikely to conflict with generic rate limiting skills or other Deepgram skills focused on different functionality. | 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 covering the full resilience stack for Deepgram API integration. Its main weakness is length — the circuit breaker and retry patterns are general-purpose code that could be more concise or split into separate files. The Deepgram-specific content (concurrency model, plan limits, usage API) is valuable and well-presented.
Suggestions
Consider extracting the full circuit breaker and retry client implementations into separate bundle files, keeping only the combined ResilientDeepgramClient usage in SKILL.md
Trim the circuit breaker implementation since it's a well-known pattern — a brief description with key parameters and the combined usage would suffice
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and provides Deepgram-specific knowledge (concurrency model, plan limits), but the code examples are quite lengthy. The circuit breaker implementation is a general pattern Claude already knows and could be more concise. The table of plan limits and the 'Key insight' callout earn their place, but the full circuit breaker class could be trimmed. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports, concrete class implementations, and production usage examples. The error handling table provides specific status codes and resolutions. The combined client pattern in Step 4 shows exactly how to wire everything together. | 3 / 3 |
Workflow Clarity | The 5-step progression is clearly sequenced from basic concurrency control through retry logic, circuit breaker, combined client, and monitoring. Each step builds on the previous one. The circuit breaker provides an explicit feedback loop (CLOSED -> OPEN -> HALF_OPEN -> CLOSED), and the retry logic includes clear validation of retryable vs non-retryable errors. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's a long monolithic file (~200 lines of code) with no bundle files to offload detail into. The circuit breaker and retry client implementations could be referenced as separate files. The Resources section at the end provides external references, which helps, 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
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.