api-throttling-setup
Api Throttling Setup - Auto-activating skill for API Development. Triggers on: api throttling setup, api throttling setup Part of the API Development skill category.
36
3%
Does it follow best practices?
Impact
96%
1.02xAverage 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-throttling-setup/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 is a very weak description that essentially just repeats the skill name without providing any meaningful detail 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., 'Configures API rate limiting, sets up request throttling middleware, defines quota policies, and implements backoff strategies.'
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about rate limiting, request throttling, API quotas, or controlling API request frequency.'
Include natural keyword variations users would say: 'rate limit', 'rate limiting', 'throttle requests', 'API quota', 'request cap', 'too many requests', '429 errors'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('API Development') and repeats the skill name ('api throttling setup') without describing any concrete actions like configuring rate limits, setting up middleware, or defining throttling policies. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when to use' clause. The 'Triggers on' line is just a duplicate of the skill name, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('api throttling setup, api throttling setup'). It misses natural variations users would say like 'rate limiting', 'request throttling', 'API rate limit', 'throttle requests', or 'request quota'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'API throttling' is somewhat specific to a niche (rate limiting/throttling), which provides some distinctiveness, but the lack of concrete details means it could overlap with general API development or rate limiting 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 only meta-descriptions about what the skill would do without providing any actual guidance on API throttling setup—no code, no configuration examples, no rate limiting strategies, no middleware patterns, and no concrete steps. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for implementing API throttling (e.g., Express rate-limit middleware, nginx rate limiting config, or API gateway throttling setup)
Provide a clear step-by-step workflow for setting up throttling, including choosing a strategy (token bucket, sliding window, etc.), configuring limits, and validating behavior under load
Replace the abstract 'Capabilities' and 'Example Triggers' sections with actual technical content such as configuration snippets, common throttling patterns, and error response formats (HTTP 429)
Add specific guidance on throttling parameters (requests per second, burst limits, retry-after headers) with concrete default values and tuning recommendations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about API throttling. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty padding. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no specific commands, no configuration snippets, no actual throttling implementation details. The entire skill describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow steps are provided whatsoever. There is no sequence of actions, no validation checkpoints, and no actual process for setting up API throttling. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-information with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to organize. | 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
3a2d27d
- 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.