rate-limiting-apis
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill rate-limiting-apisImplement sophisticated rate limiting with sliding windows, token buckets, and quotas. Use when protecting APIs from excessive requests. Trigger with phrases like "add rate limiting", "limit API requests", or "implement rate limits".
Validation
81%| 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 | |
Implementation
7%This skill claims to cover sophisticated rate limiting (sliding windows, token buckets, quotas) but delivers generic API development boilerplate instead. There are no concrete implementations, algorithms, or code examples for any rate limiting technique. The content appears to be a template that wasn't customized for the actual skill topic.
Suggestions
Add executable code examples for each rate limiting algorithm mentioned (sliding window, token bucket, quota tracking) with specific implementations
Replace generic API development prerequisites and instructions with rate-limiting-specific guidance (e.g., Redis setup for distributed rate limiting, middleware integration patterns)
Include concrete validation steps to verify rate limits work correctly (e.g., 'Test with: curl -X GET endpoint 100 times, verify 429 responses after limit')
Remove or replace the malformed instruction lists with a coherent workflow specific to implementing rate limiting in an existing API
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that doesn't relate to rate limiting specifically. Prerequisites list generic API development items, and the instructions describe general API development rather than rate limiting implementation. | 1 / 3 |
Actionability | No concrete code examples for sliding windows, token buckets, or quotas. Instructions are vague ('Generate boilerplate code', 'Implement endpoint handlers') with no executable guidance on actual rate limiting algorithms or implementations. | 1 / 3 |
Workflow Clarity | Steps are generic API development steps, not rate limiting workflow. No validation checkpoints for testing rate limits work correctly. The numbered lists appear to be malformed (two separate lists starting at 1) and don't form a coherent rate limiting implementation process. | 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 point to generic files rather than rate-limiting-specific documentation. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific technical capabilities, includes natural trigger phrases users would actually say, explicitly addresses both what and when, and carves out a distinct niche that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'sliding windows, token buckets, and quotas' - these are distinct, named rate limiting algorithms/techniques that clearly describe what the skill does. | 3 / 3 |
Completeness | Clearly answers both what ('Implement sophisticated rate limiting with sliding windows, token buckets, and quotas') AND when ('Use when protecting APIs from excessive requests' plus explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'add rate limiting', 'limit API requests', 'implement rate limits', plus 'APIs' and 'excessive requests'. These are phrases users would naturally use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on rate limiting for APIs with distinct technical terms (sliding windows, token buckets, quotas) that are unlikely to conflict with other skills. The trigger phrases are specific to this domain. | 3 / 3 |
Total | 12 / 12 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.