api-rate-limiting

Implements API rate limiting using token bucket, sliding window, and Redis-based algorithms to protect against abuse. Use when securing public APIs, implementing tiered access, or preventing denial-of-service attacks.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/api-rate-limiting/skills/api-rate-limiting/SKILL.md

Quality

Content

67%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.

The content is compact and actionable with concrete code and tables, but it presents reference material rather than a sequenced workflow and omits validation/load-testing checkpoints for a deployment-sensitive topic. Adding a brief stepwise implementation+verification flow and a runnable Redis example would raise the weaker dimensions.

Suggestions

Add a short sequenced workflow (choose algorithm -> apply middleware -> verify 429 response under load) with explicit validation/test checkpoints to lift workflow_clarity above 3.

Provide a minimal runnable Redis-based rate limiting code example instead of only a bullet hint, to close the actionability gap.

Trim the 'Best Practices' bullets and inline code comments that restate knowledge Claude already has to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is largely lean with tables and code that earn their place, though brief inline comments and the 'Best Practices' bullet list restate knowledge Claude already has; minor trimming possible.	4 / 5
Actionability	Provides copy-paste-ready TokenBucket and express-rate-limit examples plus concrete header values and tiered-limit tables, but lacks a complete runnable Redis example (only a bullet hint) leaving a small gap.	4 / 5
Workflow Clarity	Sections are organized by topic rather than as a sequenced workflow, and for rate limiting (a potentially batch/deployed operation) there are no validation checkpoints or test/load-test steps beyond a 'Test under load' bullet, capping clarity at 3.	3 / 5
Progressive Disclosure	Well-organized sections with tables and code kept appropriately inline for a single-file skill under 50 lines; no bundle files exist to reference, and structure is clear with only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

86%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.

The description is strong: it states concrete capabilities with named algorithms, provides explicit 'Use when' trigger guidance covering multiple scenarios, and occupies a distinct niche. Minor additional synonyms would round out trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists concrete actions ('Implements API rate limiting using token bucket, sliding window, and Redis-based algorithms') naming three specific algorithms, though it stops short of enumerating the full set of operational actions like tiered limits or header handling.	4 / 5
Completeness	Clearly answers both 'what' (implements rate limiting via named algorithms) and 'when' ('Use when securing public APIs, implementing tiered access, or preventing denial-of-service attacks') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrases ('securing public APIs', 'implementing tiered access', 'preventing denial-of-service attacks') that a user would plausibly say, with only minor common synonyms (e.g. 'throttling', '429') absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (rate limiting / abuse protection) with distinct triggers unlikely to fire for unrelated skills; minimal overlap risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: secondsky/claude-skills
Path: plugins/api-rate-limiting/skills/api-rate-limiting/SKILL.md
Commit: 84802a4

Reviewed: 4 days 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.