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

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-3

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

A well-organized, token-efficient skill body that uses progressive disclosure effectively and assumes Claude's competence. Its main gaps are the absence of any executable code in the body itself (despite being a code-producing skill) and a workflow whose validation is a single end-of-process step rather than an explicit feedback loop.

Suggestions

Include at least one copy-paste-ready code snippet in the body (e.g., the Redis sorted-set sliding-window limiter) so the skill is actionable without a reference hop.

Add an explicit validation feedback loop to the Instructions, e.g. after step 9: 'If threshold tests fail, re-check the client-identifier extraction and window-boundary logic, then re-run tests.'

Tighten step 9 into a concrete test command or assertion checklist (e.g., assert X-RateLimit-Remaining decrements and resets at the window boundary) rather than a descriptive instruction.

Dimension	Reasoning	Score
Conciseness	The body is lean: concrete numbered steps, a compact error table, and brief scenario examples, with no padding or explanation of concepts Claude already knows (e.g., it never explains what Redis or a token bucket is).	3 / 3
Actionability	Guidance is concrete (exact headers, tier numbers like Free 100/Pro 1000/Enterprise 10000 req/min, 2x burst for 10s, Redis commands ZRANGEBYSCORE/MULTI/EXEC/TIME) but the body contains no executable code blocks — all copy-paste-ready code is deferred to references/examples.md.	2 / 3
Workflow Clarity	A clear 9-step build sequence exists, but verification is confined to a single terminal step (step 9, 'write tests') with no inline validate→fix→retry feedback loop within the workflow; recovery guidance lives only in the separate error-handling table.	2 / 3
Progressive Disclosure	The body is an overview that clearly signals one-level-deep references (implementation.md, errors.md, examples.md), all of which are real files containing terminal content with no further nesting.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, complete description: it names concrete techniques, provides explicit 'Use when' guidance plus natural trigger phrases, and stays in third person. The only minor weakness is the mildly marketing word 'sophisticated', which is nevertheless substantiated by the listed algorithms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'sliding windows, token buckets, and quotas' — rather than vague language; the mild adjective 'sophisticated' is backed by these specific techniques.	3 / 3
Completeness	Answers both 'what' ('Implement sophisticated rate limiting with sliding windows, token buckets, and quotas') and 'when' ('Use when protecting APIs from excessive requests') with explicit triggers.	3 / 3
Trigger Term Quality	Explicitly enumerates natural trigger phrases ('add rate limiting', 'limit API requests', 'implement rate limits') that a user would plausibly say.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (rate limiting APIs) with distinct triggers unlikely to collide with other 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
Path: plugins/api-development/api-rate-limiter/skills/rate-limiting-apis/SKILL.md
Commit: 0540a62

Reviewed: 1 day 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.