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 description is extremely weak across all dimensions. It reads like auto-generated boilerplate with no actual explanation of what the skill does, what actions it performs, or meaningful trigger guidance. The repeated trigger term and lack of concrete capabilities make it nearly useless for skill selection.
Suggestions
Add concrete actions the skill performs, e.g., 'Configures rate limiting rules, sets request thresholds, defines throttling policies for APIs and endpoints.'
Expand trigger terms to include natural variations: 'rate limiting', 'throttle requests', 'API rate limits', 'request throttling', 'DDoS protection', 'request quotas'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to configure or troubleshoot rate limiting, set request thresholds, or protect services from excessive traffic.'
| 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 a repeated trigger phrase with no meaningful guidance on when Claude should select this skill. | 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', 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, it could overlap with other security-related skills since it only vaguely references 'Security Fundamentals' without clear boundaries. | 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 entirely a meta-description placeholder with no actual content. It describes what it would do ('provides step-by-step guidance,' 'generates production-ready code') without providing any of it. There is no actionable information about rate limiter configuration—no algorithms, no code examples, no configuration snippets, no security considerations.
Suggestions
Add concrete, executable code examples for common rate limiter implementations (e.g., token bucket in Python/Node.js, Redis-based sliding window, nginx rate limiting config).
Include a clear workflow: 1) Choose algorithm, 2) Configure limits, 3) Implement middleware, 4) Test with load testing tool, 5) Validate behavior under load.
Add specific configuration examples with actual values (e.g., '100 requests per minute per IP') and security considerations (e.g., how to handle distributed systems, what to return on 429).
Remove all meta-description content ('This skill provides...', 'When to Use...', 'Example Triggers...') and replace with actual technical guidance on rate limiter configuration.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler text that provides no actionable information. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty claims with no substance. The entire file explains what the skill supposedly does without ever actually doing it. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no specific rate limiter patterns, no algorithms (token bucket, sliding window, etc.), and no actual implementation details. The skill describes rather than instructs. | 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 whatsoever. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to detailed materials. There are no references to supporting files, no examples section, and no layered organization. The 'Related Skills' section is just a tag list. | 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
13d35b8
- 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.