throttling-apis
Implement API throttling policies to protect backend services from overload. Use when controlling API request rates. Trigger with phrases like "throttle API", "control request rate", or "add throttling".
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill throttling-apisActivation
N/ASomething went wrong
Implementation
7%This skill fails to teach API throttling. The content is generic API development boilerplate with no throttling-specific code, algorithms (token bucket, sliding window, etc.), rate limit configurations, or concrete examples. The numbered instructions appear corrupted with duplicate step 1s, and all substantive content is deferred to external references.
Suggestions
Add concrete throttling code examples showing token bucket or sliding window implementations with specific rate limits (e.g., '100 requests per minute')
Include executable configuration examples for common frameworks (Express rate-limiter, FastAPI slowapi, etc.) with copy-paste ready code
Fix the numbered instruction lists and add throttling-specific workflow: configure limits -> implement middleware -> test with load -> monitor and adjust
Remove generic API development content (models, controllers, authentication) that doesn't relate to throttling specifically
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that doesn't teach throttling specifically. The overview repeats itself, prerequisites list generic development setup, and the instructions describe general API development rather than throttling implementation. | 1 / 3 |
Actionability | No concrete code examples, no specific throttling algorithms or configurations, no executable commands. Instructions like 'Define resource models' and 'Add input validation' are vague directions without any throttling-specific guidance. | 1 / 3 |
Workflow Clarity | Steps are numbered but appear to be two separate lists merged incorrectly (two '1.' entries). No validation checkpoints for throttling behavior, no feedback loops, and the sequence doesn't specifically address throttling implementation at all. | 1 / 3 |
Progressive Disclosure | References to external files (implementation.md, errors.md, examples.md) are present and one-level deep, but the main content is poorly organized and the references defer all useful content elsewhere, leaving the skill body essentially empty of actionable throttling guidance. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
81%Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 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.