api-rate-limiting-config
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill api-rate-limiting-configApi Rate Limiting Config - Auto-activating skill for API Development. Triggers on: api rate limiting config, api rate limiting config Part of the API Development skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It repeats the skill name as trigger terms, provides no concrete actions or capabilities, and lacks any guidance on when Claude should select this skill. The description fails to differentiate itself or provide value for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configure API rate limits, set request quotas, implement throttling rules, define rate limit tiers'
Include a 'Use when...' clause with natural trigger terms like 'throttling', 'request limits', 'API quotas', 'too many requests', '429 errors', 'rate limiter configuration'
Remove the redundant trigger term repetition and replace with varied, natural phrases users would actually say when needing rate limiting help
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the skill name repeated. It doesn't describe what the skill actually does (e.g., configure rate limits, set throttling rules, implement quotas). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. There's no 'Use when...' clause and no description of capabilities beyond the category label. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('api rate limiting config'). Missing natural variations users would say like 'throttling', 'request limits', 'API quotas', 'rate limiter'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'API rate limiting' is somewhat specific to a niche, but without concrete actions or clear triggers, it could overlap with general API development or configuration skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is entirely meta-content describing what a skill should do rather than providing any actual guidance on API rate limiting configuration. It contains no executable code, no specific rate limiting strategies, no configuration examples, and no concrete implementation details. The content is essentially a placeholder template that fails to teach Claude anything about rate limiting.
Suggestions
Add concrete code examples showing rate limiting implementations (e.g., token bucket, sliding window algorithms) with specific libraries like express-rate-limit or similar
Include actual configuration examples with specific values (requests per minute, burst limits, response headers)
Provide a clear workflow for implementing rate limiting: 1) Choose strategy, 2) Configure middleware, 3) Set up response headers, 4) Test with load
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actionable technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual rate limiting configurations. The skill describes what it claims to do but never shows how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps, no sequence, and no validation checkpoints for implementing rate limiting - just vague claims about 'step-by-step guidance' without any actual steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no useful structure. There are no references to detailed materials, no examples section, and no actual content to organize. | 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.