CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-organized content that splits overview from full implementation cleanly and uses progressive disclosure effectively. The main weakness is the absence of an explicit validation checkpoint in the batch fan-out workflow, which caps workflow clarity at 4.

Suggestions

Add an explicit validation step to the workflow — e.g., after Step 3's queue, run a small batch and confirm `monitor.getStatus()` shows no 429s before scaling to the full fan-out.

Inline one complete copy-pasteable snippet (such as the `withRateLimitRetry` wrapper) so a reader can start without immediately opening implementation.md.

Trim the Prerequisites prose and the Rate Limits at a Glance section, which partially duplicate information already in reference.md.

DimensionReasoningScore

Conciseness

Action-dense prose that assumes competence and skips basic explanation of rate limits, with only minor trimmable prose in Overview/Prerequisites.

4 / 5

Actionability

Each step names concrete config (intervalCap, maxDelayMs, retry 429/5xx) and includes an executable inline 429 handler; full copy-paste code lives one level deep in implementation.md, leaving minor inline gaps.

4 / 5

Workflow Clarity

Five clearly sequenced, explicitly composed steps (queue → monitor → retry) with an error-handling table; lacks an explicit verify-before-proceed checkpoint for the batch fan-out case.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview pointing to two verified one-level-deep references (implementation.md, reference.md), clearly signaled with repeated inline links and no nested references.

5 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly answers both what the skill does and when to use it with concrete trigger phrases. Minor gaps in capability coverage (proactive monitoring, model fallback) keep specificity at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several concrete actions — "backoff, queuing, and header parsing" — covering multiple distinct capabilities, with minor gaps (proactive monitoring and model fallback are absent).

4 / 5

Completeness

Explicitly states both what it does ("Implement Groq rate limit handling with backoff, queuing, and header parsing") and when to use it, plus concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Provides five natural, user-sayable phrases ("groq rate limit", "groq throttling", "groq 429", "groq retry", "groq backoff"), though a few synonyms like "groq api limit" are missing.

4 / 5

Distinctiveness Conflict Risk

The "Groq" prefix on every capability and trigger phrase carves out a clear niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/tons-of-skills-marketplace
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.