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".
89
88%
Does it follow best practices?
Impact
—
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 listing concrete trigger terms. The narrow, well-defined domain makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'backoff', 'queuing', and 'header parsing' for Groq rate limit handling. These are distinct, concrete 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 explicit trigger phrases). | 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 API rate limiting. The combination of 'Groq' + 'rate limit' creates a very clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 spectrum of Groq rate limit handling. The workflow is well-sequenced with proper feedback loops and error recovery. The main weakness is that it's somewhat long for a single file — the advanced patterns (proactive monitoring, model fallback) could be split into referenced files — and some reference tables explain concepts Claude already understands.
Suggestions
Consider moving Steps 4-5 (RateLimitMonitor and smartModelSelect) into a separate ADVANCED.md file, keeping SKILL.md focused on the core retry + queue pattern.
Remove or condense the RPM/TPD/RPD/TPM constraint table — Claude already knows these acronyms; a single sentence suffices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The rate limit structure table and header table provide useful reference, but some content is somewhat verbose — the model-aware strategy section and error handling table add bulk that could be trimmed. The tables explaining RPM/TPM/RPD/TPD are borderline unnecessary since Claude knows these acronyms. Overall mostly efficient but not maximally lean. | 2 / 3 |
Actionability | Every step includes fully executable TypeScript code with proper imports, typed interfaces, and real Groq SDK usage. The code is copy-paste ready with concrete error handling patterns, queue configuration, and monitoring logic. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced from basic header parsing through retry logic, queuing, proactive monitoring, and model fallback. Each step builds on the previous one, and validation/feedback loops are embedded (retry-after checking, shouldThrottle checks, waitIfNeeded). The error handling table provides clear symptom-to-solution mappings. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a logical progression, but it's quite long for a single SKILL.md with no bundle files. The detailed code for Steps 4 and 5 (proactive monitor, model-aware selection) could reasonably be split into separate reference files. The single reference to 'groq-security-basics' is appropriate but the skill itself is monolithic. | 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.