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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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

The content is highly actionable and concise with strong executable examples and a clear step sequence. Its main weaknesses are the absence of explicit validation checkpoints for batch/queue operations and a monolithic single-file structure with no progressive disclosure into bundle files.

Suggestions

Add explicit validation/verification checkpoints (e.g., assert remaining-quota reads succeed, verify queue drain before proceeding) to the queue and monitor workflows to lift workflow clarity.

Move the longer implementations (e.g., the RateLimitMonitor class or the queue setup) into a references/ file and link to it from a concise overview, so the main body stays a lean entry point.

Add a short 'Verify' step at the end of the retry/queue flow that confirms a successful 200 response and updated quota headers before declaring the operation complete.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it uses compact tables and executable code rather than explaining what rate limits or headers are, with every section earning its place. It sits just above the verbosity threshold but does not pad with concepts Claude already knows.	3 / 3
Actionability	Five complete, executable TypeScript implementations plus specific header names and concrete error-handling guidance make the skill copy-paste ready, matching the fully-executable anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Parse Headers → Backoff → Queue → Monitor → Model-Aware), but there are no explicit validation checkpoints or feedback loops, and the queue/batch operations would benefit from validate-style checkpoints — capping this at 2 per the batch-operations guideline.	2 / 3
Progressive Disclosure	The single file is well-organized into labeled sections, but all five full code implementations and reference tables live inline in a ~220-line monolith with no bundle files to offload detail into, so structure is present but not split.	2 / 3
	Total	10 / 12 Passed

Description

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.

The description is concise, third-person imperative, and clearly states both capability and trigger conditions with natural user phrasing. It is a strong, well-targeted description.

Dimension	Reasoning	Score
Specificity	Names concrete, multiple actions — 'backoff, queuing, and header parsing' — tied to a clear domain, matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers what ('Implement Groq rate limit handling with backoff, queuing, and header parsing') and when ('Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput'), satisfying both halves.	3 / 3
Trigger Term Quality	Provides natural phrases users would say — 'groq rate limit', 'groq throttling', 'groq 429', 'groq retry', 'groq backoff' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear Groq-specific niche with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 1628598

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.