throttling-apis

Implement API throttling policies to protect backend services from overload. Use when controlling API request rates. Trigger with phrases like "throttle API", "control request rate", or "add throttling".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

A well-organized, lean overview that uses progressive disclosure effectively and sequences its workflow with validation. The main gap is actionability: concrete code lives in reference files rather than inline in the body.

Suggestions

Add one short inline code snippet or copy-paste command in the Instructions (e.g., a minimal concurrency-limiter middleware) so the body is actionable without opening references.

Surface a quick-start example directly in the body and keep the deeper examples.md for variations, raising inline actionability.

Include a one-line validation command (e.g., a k6 invocation) in step 8 rather than only describing the load test to write.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it does not lecture on what circuit breakers or throttling are, and every section earns its place without padding.	3 / 3
Actionability	The instructions give specific, concrete values (503, Retry-After, 5 failures in 10s, p95/p99, named X-Throttle headers), but the main body contains no inline executable code or commands — that detail lives in references — so it stops short of copy-paste-ready guidance.	2 / 3
Workflow Clarity	An 8-step numbered sequence with an explicit validation step (load tests verifying throttle engagement and recovery) plus an error-handling table providing feedback loops meets the highest anchor.	3 / 3
Progressive Disclosure	The body is a clear overview with well-signaled, one-level-deep references to real files (implementation.md, errors.md, examples.md), with content appropriately split across them.	3 / 3
	Total	11 / 12 Passed

Description

90%

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 well-formed description with explicit "what" and "when" guidance plus natural trigger phrases. Its only weakness is single-action specificity rather than enumerating multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and a concrete action ("Implement API throttling policies to protect backend services from overload"), but describes a single action rather than listing multiple specific concrete actions, so it falls short of a 3.	2 / 3
Completeness	Explicitly answers both "what" (implement throttling policies to protect backends) and "when" via the "Use when controlling API request rates" clause, meeting the highest anchor.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say — "throttle API", "control request rate", "add throttling" — giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	API throttling is a clear niche with distinct triggers ("throttle API", "control request rate"), making it unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 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: about 21 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.