rate-limit-middleware
Rate Limit Middleware - Auto-activating skill for Backend Development. Triggers on: rate limit middleware, rate limit middleware Part of the Backend Development skill category.
33
Quality
3%
Does it follow best practices?
Impact
85%
1.08xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/rate-limit-middleware/SKILL.mdQuality
Discovery
7%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 description is essentially a placeholder that provides almost no useful information for skill selection. It names the topic but fails to describe capabilities, actions, or meaningful trigger conditions. The repeated trigger term and boilerplate structure suggest auto-generated content that needs substantial human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Implements rate limiting middleware to throttle API requests, configure request quotas, handle 429 responses, and set up sliding window or token bucket algorithms.'
Include a 'Use when...' clause with natural trigger terms: 'Use when implementing request throttling, API rate limits, preventing abuse, handling too many requests errors, or configuring request quotas.'
Add context about supported frameworks or languages to improve distinctiveness, e.g., 'for Express.js/Node.js applications' or 'across Python, Node, and Go backends.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain 'Rate Limit Middleware' without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what the skill actually does (e.g., configure limits, implement throttling, set up request quotas). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the topic, and provides no explicit 'when to use' guidance. The 'Triggers on' section is just the skill name repeated, not meaningful trigger conditions. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('rate limit middleware' repeated twice) and miss natural variations users might say like 'throttling', 'request limits', 'API rate limiting', 'too many requests', or '429 errors'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'rate limit middleware' is a specific enough domain that it wouldn't conflict with most skills, the lack of detail about what kind of rate limiting (API, web, database) or what framework/language could cause overlap with other backend or API-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is a template placeholder with no actual technical value. It contains zero implementation details for rate limit middleware - no code examples, no configuration patterns, no library recommendations, and no workflow guidance. The entire content describes what the skill claims to do rather than actually teaching Claude how to implement rate limiting.
Suggestions
Add concrete, executable code examples for rate limiting in Node.js, Python, and Go (e.g., express-rate-limit, Flask-Limiter, golang.org/x/time/rate)
Include specific configuration patterns: sliding window vs fixed window, Redis-backed distributed rate limiting, response headers (X-RateLimit-Remaining, Retry-After)
Provide a clear workflow: 1) Choose algorithm, 2) Configure limits, 3) Implement middleware, 4) Test with load testing tool, 5) Monitor and adjust
Add references to detailed implementation files for each language/framework rather than generic capability claims
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no actual technical substance. It explains what the skill does in abstract terms without providing any concrete implementation details, wasting tokens on meta-descriptions Claude doesn't need. | 1 / 3 |
Actionability | No executable code, no concrete commands, no specific examples of rate limiting implementations. The content only describes what the skill could do rather than providing actual guidance on implementing rate limit middleware. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains zero actual steps. No validation checkpoints, no sequence of operations, nothing actionable for implementing rate limiting. | 1 / 3 |
Progressive Disclosure | No structure beyond boilerplate headings. No references to detailed implementation guides, no links to examples or API documentation. The content is a shallow placeholder with no depth or navigation to actual resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
994edc4
- 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.