api-rate-limiting-config
Api Rate Limiting Config - Auto-activating skill for API Development. Triggers on: api rate limiting config, api rate limiting config Part of the API Development skill category.
34
3%
Does it follow best practices?
Impact
86%
0.97xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/15-api-development/api-rate-limiting-config/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 restates the skill name without providing any meaningful information about what the skill does or when it should be used. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates rate limiting middleware, configures throttling policies, sets request quotas and burst limits for API endpoints.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about rate limiting, throttling, request quotas, API abuse prevention, or configuring request limits.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'rate limit', 'throttle', 'request quota', 'API limits', 'burst rate'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It merely names the topic 'API Rate Limiting Config' without describing what the skill actually does (e.g., configure rate limits, set throttling policies, generate middleware code). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explicit 'Use when...' clause and no description of capabilities beyond the title. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('api rate limiting config, api rate limiting config'). There are no natural user-language variations like 'throttling', 'rate limit', 'request limits', 'API throttle', or 'quota'. | 1 / 3 |
Distinctiveness Conflict Risk | The topic 'API rate limiting config' is a reasonably specific niche, which provides some distinctiveness. However, the lack of concrete actions or triggers means it could still overlap with general API development 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 is essentially a placeholder with no substantive content. It contains no actionable information about API rate limiting configuration—no code, no algorithms (token bucket, sliding window, etc.), no configuration examples, no library recommendations, and no concrete guidance of any kind. It merely restates its own title in various ways across multiple sections.
Suggestions
Add concrete, executable code examples for common rate limiting implementations (e.g., token bucket with Redis, Express middleware, nginx config, API gateway settings).
Include specific configuration snippets for popular frameworks/tools (e.g., express-rate-limit, Kong, AWS API Gateway) with actual parameter values and explanations of key settings.
Define a clear workflow: 1) Choose rate limiting strategy, 2) Configure limits, 3) Implement middleware/gateway rules, 4) Test with load testing tools, 5) Monitor and adjust.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual technical content about rate limiting patterns, headers (X-RateLimit-Limit, Retry-After), and response codes (429).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about API rate limiting configuration. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no configuration snippets, no specific rate limiting algorithms, no library recommendations, no commands. It only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive block with no meaningful structure. Sections like 'Capabilities' and 'Example Triggers' add no value. There are no references to detailed materials or external files. | 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
4dee593
- 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.