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
Quality
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 description is severely underdeveloped, functioning more as a label than a useful skill description. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use it. The repetitive trigger terms and absence of a 'Use when...' clause make it nearly useless for skill selection among multiple options.
Suggestions
Add specific actions the skill performs, e.g., 'Configures API rate limits, implements request throttling, sets up quota management, and creates backoff retry logic.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions rate limiting, request throttling, API quotas, preventing API abuse, or limiting request frequency.'
Add variations of trigger terms users might naturally say: 'rate limit', 'throttle', 'request quota', 'API limits', 'prevent overload', '429 errors'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Api Throttling Setup' 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 rate limits, set up request quotas, implement backoff strategies). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides a category label ('API Development') without explaining capabilities or explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The triggers listed are just 'api throttling setup' repeated twice. This misses natural variations users might say like 'rate limiting', 'request limits', 'API quotas', 'throttle requests', or 'limit API calls'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'throttling' is somewhat specific within API development, the lack of detail means it could overlap with general API configuration skills. The term 'API Development' category is broad and doesn't help distinguish this from other 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 is a generic template with no actual content about API throttling. It contains only meta-descriptions of what a skill should do without any concrete implementation guidance, code examples, or specific throttling patterns. The content would be identical if you replaced 'api throttling setup' with any other topic.
Suggestions
Add concrete code examples showing throttling implementation (e.g., rate limiting middleware in Express, FastAPI, or similar frameworks)
Include specific throttling patterns: token bucket, sliding window, fixed window with actual configuration examples
Provide a clear workflow: 1) Choose throttling strategy, 2) Configure limits, 3) Implement middleware, 4) Test with load testing tools
Add references to common libraries/tools (e.g., express-rate-limit, slowapi, Redis-based solutions) with executable setup code
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about API throttling. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or specific implementation guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance on API throttling setup. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content claims to provide 'step-by-step guidance' but contains zero actual steps for implementing API throttling. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, examples, or related files. The content is a shallow placeholder with no depth or navigation to actual implementation details. | 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.