rate-limiting-apis

Implement sophisticated rate limiting with sliding windows, token buckets, and quotas. Use when protecting APIs from excessive requests. Trigger with phrases like "add rate limiting", "limit API requests", or "implement rate limits".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

The body is well-structured with a clear workflow, validation, and well-signaled references to real bundle files. Its main weakness is actionability: the skill promises JS source files in its Output section yet provides no executable code, and Examples are prose rather than runnable snippets.

Suggestions

Add a small executable code snippet (e.g., a rate-limiter-flexible or Redis Lua check-and-increment example) so the body has copy-paste-ready guidance, not just prose descriptions.

Replace the descriptive Examples paragraphs with at least one concrete before/after or code+output example to lift actionability.

Tighten the Examples section so it does not restate tier numbers and burst rules already covered in the Instructions, improving token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and avoids explaining generic concepts, but the Examples section partly restates the Instructions and the nine-step list plus prose examples could be tightened; not yet the lean 'every token earns its place' level.	2 / 3
Actionability	Guidance is concrete and specific (exact tiers, X-RateLimit-* headers, 429 + Retry-After, algorithm-to-use-case mapping), but the body contains no executable code and the Examples are descriptive prose rather than copy-paste snippets, so it stops short of the top anchor.	2 / 3
Workflow Clarity	A clearly sequenced nine-step process with an explicit validation step ('Write tests that verify rate limits engage at exact thresholds...') and an Error Handling table providing cause/solution feedback for recovery.	3 / 3
Progressive Disclosure	A concise overview in SKILL.md with well-signaled, one-level-deep references to real files (implementation.md, errors.md, examples.md, all present in references/); content is appropriately split and easy to navigate.	3 / 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, and concrete: it names the algorithms, gives an explicit 'Use when' trigger, and lists natural trigger phrases. It is a strong description with no missing what/when component.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete mechanisms — 'sliding windows, token buckets, and quotas' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both 'what' (implement rate limiting with named algorithms) and 'when' ('Use when protecting APIs from excessive requests') with explicit triggers, hitting the top anchor.	3 / 3
Trigger Term Quality	Provides natural user phrasings ('add rate limiting', 'limit API requests', 'implement rate limits') alongside a 'Use when' clause, giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (API rate limiting) with distinct, specific triggers unlikely to fire for unrelated skills; the only mild ding is 'sophisticated' being a light buzzword, but it does not blur the niche.	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: 2cafb23

Reviewed: 33 minutes 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.