groq-rate-limits
Implement Groq rate limit handling with backoff, queuing, and header parsing. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Groq. Trigger with phrases like "groq rate limit", "groq throttling", "groq 429", "groq retry", "groq backoff".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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-crafted skill description that clearly defines its scope (Groq rate limit handling), lists specific capabilities (backoff, queuing, header parsing), and provides explicit trigger guidance with natural user phrases. It follows best practices by using third person voice, including a 'Use when' clause, and enumerating trigger terms that cover common variations.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'backoff', 'queuing', and 'header parsing' for Groq rate limit handling. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement Groq rate limit handling with backoff, queuing, and header parsing) and 'when' (explicit 'Use when' clause covering rate limit errors, retry logic, and API throughput optimization, plus a 'Trigger with' clause). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'groq rate limit', 'groq throttling', 'groq 429', 'groq retry', 'groq backoff', plus broader terms like 'retry logic' and 'API request throughput'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific focus on Groq as a provider and rate limiting as the domain. The combination of 'Groq' + 'rate limit' creates a very clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 highly actionable skill with excellent, executable TypeScript code covering the full spectrum of Groq rate limit handling. Its main weaknesses are verbosity (the full inline implementation of 5 steps makes it token-heavy) and lack of explicit validation checkpoints in the workflow. Splitting advanced features (monitoring, model fallback) into a separate file would improve both conciseness and progressive disclosure.
Suggestions
Move Steps 4 (RateLimitMonitor) and 5 (smartModelSelect) into a separate ADVANCED.md file, keeping SKILL.md focused on the core parse-retry-queue workflow.
Add a validation checkpoint after Step 3, such as a quick test snippet to verify the queue and retry logic work against the Groq API before deploying in production.
Remove the Rate Limit Structure table — Claude already knows what RPM/TPM/RPD/TPD mean, and the table adds tokens without actionable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes useful information but is verbose for what it covers. The rate limit structure table and some explanatory text (e.g., 'Groq rate limits vary by plan and model') add tokens without much value Claude wouldn't already know. The code examples are substantial but justified given the complexity. Steps 4 and 5 add significant length for features that may not always be needed. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports, types, and error handling. The header parsing, retry logic, queue setup, and monitoring are all copy-paste ready with concrete implementations rather than pseudocode. | 3 / 3 |
Workflow Clarity | The steps are clearly numbered and sequenced (parse headers → retry logic → queue → monitor → model selection), but there are no explicit validation checkpoints or feedback loops. For API operations that could fail in cascading ways, there's no guidance on verifying the setup works correctly or testing the retry behavior. | 2 / 3 |
Progressive Disclosure | The content is mostly monolithic — all five steps with full code implementations are inline in a single file. Steps 4 and 5 (proactive monitoring, model-aware selection) could be split into a separate advanced reference file. The error handling table and resources section are well-organized, and there's a reference to groq-security-basics, but the main body is quite long. | 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
4dee593
- 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.