CtrlK

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.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill rate-limiter-config

What are skills?

Overall
score

19%

Review — 4%

Does it follow best practices?

Validation — 11 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Activation

This description is severely underdeveloped, functioning more as a category label than a useful skill description. It provides no information about what actions the skill enables, what problems it solves, or when Claude should select it. The redundant trigger terms and boilerplate structure suggest auto-generated content without meaningful customization.

Suggestions

Add specific actions the skill performs, e.g., 'Configures rate limiting rules, sets request thresholds, implements throttling patterns for APIs and web services.'

Include a proper 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user asks about preventing API abuse, setting request limits, configuring throttling, or protecting endpoints from excessive traffic.'

Add varied trigger terms users would naturally say: 'throttling', 'request limits', 'API protection', 'DDoS prevention', 'traffic control'.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions - it only states it's an 'auto-activating skill' without explaining what it actually does. No verbs describing capabilities like 'configure', 'set limits', or 'protect endpoints' are present.	1 / 3
Completeness	The description fails to answer 'what does this do' beyond naming itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' line is not a proper 'Use when...' clause with context.	1 / 3
Trigger Term Quality	The trigger terms listed are redundant ('rate limiter config' repeated twice) 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 domain, the lack of detail about what aspects of rate limiting it handles (configuration syntax, implementation patterns, specific frameworks) means it could overlap with general security or API skills.	2 / 3
	Total	5 / 12 Passed

Implementation

This skill is essentially a placeholder with no actual instructional content. It describes what a rate limiter config skill should do without providing any concrete guidance, code examples, configuration patterns, or implementation details. The entire content could be replaced with actual rate limiting configurations, code snippets, and security considerations.

Suggestions

Add concrete code examples for common rate limiter implementations (e.g., token bucket, sliding window) with specific libraries like express-rate-limit, redis-based limiters, or nginx configurations

Include specific configuration parameters with recommended values (requests per minute, burst limits, response codes, headers to return)

Provide a workflow for implementing rate limiting: identify endpoints -> choose algorithm -> configure limits -> add monitoring -> test under load

Add security-specific guidance: how rate limiting prevents DDoS, brute force attacks, and API abuse, with concrete threshold recommendations

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual technical content.	1 / 3
Actionability	There is zero concrete guidance - no code, no commands, no specific configurations, no examples of actual rate limiter implementations. The skill describes what it claims to do rather than providing any executable instructions.	1 / 3
Workflow Clarity	No workflow is defined. The skill mentions 'step-by-step guidance' but provides none. There are no steps, no validation checkpoints, and no actual process for configuring rate limiters.	1 / 3
Progressive Disclosure	The content is a flat, uninformative structure with no references to detailed materials, no links to configuration examples, and no organization beyond generic section headers that contain no useful content.	1 / 3
	Total	4 / 12 Passed

Validation

69%

Warnings & errors only

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: 22 days ago

Table of Contents

Activation Implementation Validation

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.