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.
92
89%
Does it follow best practices?
Impact
95%
1.15xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is a well-crafted skill description that excels across all dimensions. It provides specific implementation approaches (token bucket, sliding window, Redis-based), includes natural trigger terms users would use when needing rate limiting help, and clearly separates the 'what' from the 'when' with an explicit 'Use when...' clause. The description is distinctive enough to avoid conflicts with general API or security skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'token bucket, sliding window, and Redis-based algorithms' and specific purposes 'protect against abuse'. Names specific implementation approaches rather than vague language. | 3 / 3 |
Completeness | Clearly answers both what ('Implements API rate limiting using token bucket, sliding window, and Redis-based algorithms') AND when ('Use when securing public APIs, implementing tiered access, or preventing denial-of-service attacks') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'rate limiting', 'API', 'token bucket', 'sliding window', 'Redis', 'abuse', 'tiered access', 'denial-of-service attacks', 'DoS'. Good coverage of both technical and problem-oriented terms. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on rate limiting with distinct algorithm mentions (token bucket, sliding window, Redis-based). Unlikely to conflict with general API or security skills due to specific focus on rate limiting patterns. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, concise skill with excellent executable code examples for rate limiting. The main weaknesses are the lack of a clear implementation workflow (when to use which algorithm, how to verify it's working) and incomplete coverage of the Redis-based approach mentioned in the description. Best practices section is a bullet list without actionable guidance.
Suggestions
Add a brief workflow section showing the decision process: 1) Choose algorithm based on use case, 2) Implement, 3) Verify with test requests, 4) Monitor in production
Include Redis-based implementation code since it's mentioned in the description and best practices but not demonstrated
Convert 'Best Practices' bullets into actionable guidance or link to a separate BEST_PRACTICES.md with detailed examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. Tables, code examples, and headers convey information without padding or explaining concepts Claude already knows. | 3 / 3 |
Actionability | Provides fully executable code for both custom TokenBucket implementation and Express middleware. Code is copy-paste ready with clear configuration options and response header examples. | 3 / 3 |
Workflow Clarity | Content presents components (algorithm, middleware, headers) but lacks a clear workflow sequence for implementation. No validation steps or guidance on testing the rate limiter is working correctly before deployment. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but mentions Redis for distributed rate limiting without providing implementation or linking to a reference. The skill could benefit from separating advanced topics (Redis implementation, monitoring) into referenced files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
90d6bd7
- Reviewed
Table of Contents
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.