rate-limiter-config
Rate Limiter Config - Auto-activating skill for Security Fundamentals. Triggers on: rate limiter config, rate limiter config Part of the Security Fundamentals skill category.
38
Quality
7%
Does it follow best practices?
Impact
98%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/03-security-fundamentals/rate-limiter-config/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 placeholder than a useful skill description. It lacks any concrete actions, meaningful trigger terms, or guidance on when Claude should select this skill. The duplicated trigger term suggests a template that wasn't properly filled out.
Suggestions
Add specific actions the skill performs, e.g., 'Configures rate limiting rules, sets request thresholds, defines throttling policies for APIs and endpoints.'
Include a 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user asks about limiting API requests, preventing abuse, throttling traffic, or configuring request quotas.'
Add natural keyword variations users might say: 'throttling', 'request limits', 'API quotas', 'DDoS protection', 'traffic control'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain 'Rate Limiter Config' but provides no concrete actions. There are no verbs describing what the skill actually does (e.g., configure, set limits, define thresholds). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the topic, and provides no explicit 'when to use' guidance. The 'Triggers on' clause just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are duplicated ('rate limiter config, rate limiter config') and overly technical. Missing natural variations users might say like 'throttling', 'request limits', 'API rate limiting', or 'prevent abuse'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'rate limiter' is somewhat specific to a security/infrastructure niche, the lack of detail about what aspects of rate limiting it handles (configuration, monitoring, implementation) could cause overlap with other security or API-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%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 hollow template with no actual content about rate limiter configuration. It describes capabilities in abstract terms but provides zero actionable guidance, code examples, configuration patterns, or implementation details. The skill would be useless for actually helping with rate limiting tasks.
Suggestions
Add concrete code examples showing rate limiter implementation (e.g., token bucket, sliding window algorithms) in at least one language/framework
Include specific configuration examples with actual values (requests per second, burst limits, key strategies)
Provide a clear workflow: 1) Choose algorithm, 2) Configure limits, 3) Implement middleware/decorator, 4) Test with load
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about rate limiter configuration. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, configuration examples, or specific implementation details are provided. The skill describes what it does abstractly but never shows how to actually configure a rate limiter. | 1 / 3 |
Workflow Clarity | No steps, sequences, or processes are defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for implementing rate limiting. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, but there are no references to detailed documentation, examples, or related files. The structure exists but contains no substantive content to disclose. | 2 / 3 |
Total | 5 / 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
994edc4
- 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.