api-throttling-setup
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill api-throttling-setupApi Throttling Setup - Auto-activating skill for API Development. Triggers on: api throttling setup, api throttling setup Part of the API Development skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without providing any meaningful information about capabilities or usage triggers. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. The redundant trigger terms and boilerplate category mention do not compensate for the missing substantive content.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures rate limiting rules, implements request throttling middleware, sets up API quotas and burst limits'
Include a 'Use when...' clause with natural trigger terms like 'rate limiting', 'request limits', 'API quotas', 'throttle', 'limit requests per second', 'prevent API abuse'
Remove the redundant duplicate trigger term and expand with variations users would naturally say when needing this functionality
| 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, implement throttling middleware, set up quotas). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no explanation of the skill's functionality beyond its name. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'api throttling setup' repeated twice, which is redundant and lacks natural variations users might say like 'rate limiting', 'request limits', 'API quotas', 'throttle requests', or 'limit API calls'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'API throttling' is a somewhat specific domain, the lack of detail means it could overlap with general API development skills. The mention of 'API Development skill category' provides some context but doesn't clearly distinguish this skill's unique purpose. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template that provides no actual guidance on API throttling setup. It contains only meta-descriptions of what the skill claims to do without any concrete implementation details, code examples, or actionable instructions. The content would be identical if you replaced 'api throttling setup' with any other topic.
Suggestions
Add concrete code examples showing rate limiting implementation (e.g., token bucket algorithm, sliding window) with specific middleware/framework examples
Include specific configuration examples for common API frameworks (Express.js rate-limiter, Django REST throttling, etc.)
Provide a clear workflow: 1) Choose throttling strategy, 2) Configure limits, 3) Implement middleware, 4) Test with load testing tools, 5) Monitor and adjust
Remove all generic boilerplate text and replace with actual technical content about throttling patterns, HTTP 429 responses, and retry-after headers
| 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 doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific implementation guidance is provided. The skill describes what it does abstractly but never shows how to actually implement API throttling (rate limiting algorithms, middleware setup, configuration examples). | 1 / 3 |
Workflow Clarity | No workflow or steps are provided. The 'Capabilities' section mentions 'step-by-step guidance' but none is actually included in the skill content. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no meaningful structure. There are no references to detailed documentation, examples, or related resources that would help with actual implementation. | 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.