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
Quality
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 with no substantive content. It repeats the skill name as trigger terms, provides no concrete actions or capabilities, and lacks any 'Use when...' guidance. The description fails to help Claude distinguish when to select this skill over others.
Suggestions
Add specific actions the skill performs, e.g., 'Configures rate limiting rules, sets request quotas, implements throttling policies, and defines burst limits for API endpoints.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions rate limiting, throttling, request quotas, API limits, burst limits, or needs to prevent API abuse.'
Add varied trigger terms users would naturally say: 'rate limiter', 'throttle requests', 'API quotas', 'request limits', 'prevent abuse', '429 errors'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only names the topic 'API rate limiting config' without describing what the skill actually does (e.g., configure limits, set thresholds, implement throttling). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it' - it only states the category and repeats the skill name without any functional description or explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('api rate limiting config, api rate limiting config'), showing no variation or natural user language like 'throttling', 'request limits', 'rate limiter', or 'API quotas'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'rate limiting' is a somewhat specific domain within API development, the lack of concrete details means it could overlap with general API configuration or security skills without clear differentiation. | 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 actionable content. It describes what a rate limiting skill should do but provides zero implementation details, code examples, configuration patterns, or concrete guidance. The entire content could be replaced with actual rate limiting implementations (token bucket, sliding window, etc.) with code examples.
Suggestions
Add concrete code examples for common rate limiting algorithms (token bucket, sliding window, fixed window) with executable implementations
Include specific configuration examples for popular frameworks/tools (nginx, Redis, API gateways) with actual config snippets
Define a clear workflow for implementing rate limiting: 1) Choose algorithm, 2) Configure limits, 3) Implement middleware, 4) Test with load, 5) Monitor and adjust
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about API rate limiting. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, configurations, or specific guidance is provided. The skill describes what it does abstractly but never shows how to actually implement rate limiting (no algorithms, no code examples, no configuration snippets). | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequences for implementing rate limiting. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, examples, or related documentation. No structure for discovery or navigation to deeper content. | 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
0c08951
- 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.