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.
36
3%
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 is a very weak description that reads like auto-generated boilerplate. It fails to describe any concrete capabilities, repeats the same trigger term twice, and provides no meaningful guidance for when Claude should select this skill. It would be nearly indistinguishable from other security skills without more specific action descriptions.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Configures rate limiting rules, sets request thresholds, defines throttling policies, and manages IP-based access controls.'
Add an explicit 'Use when...' clause with natural trigger terms like 'rate limiting', 'throttle requests', 'API rate limits', 'request quotas', 'DDoS mitigation', 'too many requests'.
Remove the duplicate trigger term 'rate limiter config' and replace with diverse natural language variations users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only states it's an 'auto-activating skill for Security Fundamentals' without describing what it actually does — no verbs like 'configure', 'set limits', 'throttle requests', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and the 'when' clause is essentially just repeating the skill name as a trigger. There is no meaningful 'Use when...' guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'rate limiter config' repeated twice. This is a narrow technical phrase that misses natural variations users might say like 'rate limiting', 'throttling', 'request limits', 'API rate limits', 'DDoS protection', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'rate limiter config' is somewhat specific to a niche domain, which reduces conflict risk with unrelated skills. However, the lack of detail about what it actually does could cause confusion with other security-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It consists entirely of auto-generated boilerplate that describes what a rate limiter config skill would do without providing any actual guidance, code, configuration examples, or technical information about rate limiting. It fails on every dimension because there is nothing actionable or instructive in the content.
Suggestions
Add concrete, executable code examples for common rate limiter configurations (e.g., token bucket, sliding window) in at least one language/framework such as Express.js middleware or nginx config.
Include specific configuration parameters with recommended values (e.g., requests per window, window size, burst limits) and explain the security tradeoffs.
Add a clear workflow: 1) Identify endpoints to protect, 2) Choose rate limiting strategy, 3) Implement configuration, 4) Validate with test requests showing 429 responses.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') and replace with actual technical content about rate limiter configuration.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about rate limiter configuration. Every section describes the skill rather than teaching it. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no specific rate limiting algorithms or parameters. The content only describes what it would do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content has section headers but they contain only boilerplate meta-descriptions. There are no references to detailed materials, no examples to navigate to, and no meaningful content organization. | 1 / 3 |
Total | 4 / 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
c8a915c
- 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.