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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill rate-limit-middlewareOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting mostly of boilerplate metadata rather than actionable content. It fails to explain what the skill does, when to use it, or provide meaningful trigger terms. The repeated trigger term and lack of concrete capabilities make this description nearly useless for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Implements rate limiting middleware to throttle API requests, configure request quotas, and handle 429 responses'
Include a 'Use when...' clause with explicit triggers like 'Use when implementing API throttling, preventing abuse, configuring request limits, or handling too many requests errors'
Expand trigger terms to include natural variations: 'throttling', 'request limits', 'API rate limiting', '429 errors', 'request quotas', 'abuse prevention'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the concept 'Rate Limit Middleware' without describing any concrete actions. It doesn't explain what the skill actually does (e.g., configure rate limits, implement throttling, set 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 not a proper use-case explanation. | 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 'request quotas'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'rate limit middleware' is a specific enough concept to avoid broad conflicts, the lack of detail about what kind of rate limiting (API, web, specific frameworks) could cause overlap with other backend or API-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill contains no actionable content whatsoever - it is entirely self-referential metadata describing what the skill claims to do without actually teaching anything about rate limit middleware. There is no code, no implementation guidance, no examples of rate limiting algorithms, no middleware patterns, and no language-specific implementations despite claiming to cover Node.js, Python, and Go.
Suggestions
Add concrete, executable code examples for rate limiting middleware in at least one language (e.g., Express.js middleware with token bucket or sliding window algorithm)
Include specific rate limiting patterns with implementation details: token bucket, sliding window, fixed window, with pros/cons for each
Provide a clear workflow for implementing rate limiting: 1) Choose algorithm, 2) Configure limits, 3) Implement middleware, 4) Add response headers, 5) Test with load
Remove all meta-description content ('This skill activates when...') and replace with actual technical guidance that Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely meta-description about when the skill activates and what it claims to do, without any actual technical content. It explains obvious things like 'provides step-by-step guidance' without providing any guidance. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it could do ('generates production-ready code') but contains zero actual implementation examples for rate limiting middleware. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for implementing rate limiting, no validation checkpoints, and no actual process to follow. The content is purely descriptive metadata. | 1 / 3 |
Progressive Disclosure | No structure for actual content exists. There are no references to detailed documentation, no code examples to organize, and no meaningful content hierarchy beyond boilerplate section headers. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.