klingai-rate-limits

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-rate-limits

Handle Kling AI rate limits with proper backoff strategies. Use when experiencing 429 errors or building high-throughput systems. Trigger with phrases like 'klingai rate limit', 'kling ai 429', 'klingai throttle', 'klingai backoff'.

58%

Overall

Validation — 81%

Implementation — 22%

Activation — 90%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
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

	Total	13 / 16 Passed

Implementation

22%

This skill is essentially a table of contents with no actionable content. It describes rate limit handling concepts at a high level but provides zero executable code, no specific detection patterns for 429 errors, and no actual backoff implementation. The skill defers all useful content to external references while the main body offers only abstract guidance.

Suggestions

Add executable code examples for detecting 429 responses and implementing exponential backoff (e.g., a complete Python function with retry decorator or async backoff logic)

Include specific rate limit values or detection patterns for Kling AI's 429 responses, including relevant headers to check

Add a concrete validation step showing how to verify backoff is working (e.g., logging retry attempts, checking delay intervals)

Replace abstract instructions like 'Implement Detection' with actual code snippets that can be copy-pasted and used immediately

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes some unnecessary padding like 'This skill teaches' and prerequisites that Claude would already know (HTTP status codes, Python/Node versions). The actual instructions are too high-level to be useful.	2 / 3
Actionability	The instructions are entirely abstract ('Implement Detection', 'Add Backoff') with no concrete code, commands, or specific examples. There's no executable guidance - just vague descriptions of what to do without showing how.	1 / 3
Workflow Clarity	While steps are numbered, they lack any concrete detail or validation checkpoints. For rate limit handling (which involves retry logic and error recovery), there are no feedback loops, no specific detection criteria, and no validation that backoff is working correctly.	1 / 3
Progressive Disclosure	References to external files (errors.md, examples.md) are present and one-level deep, but the main content is too sparse - it defers almost all useful content to other files while providing no actionable quick-start material in the skill itself.	2 / 3
	Total	6 / 12 Passed

Activation

90%

This is a well-structured skill description with excellent trigger term coverage and clear 'Use when' guidance. The main weakness is that the capabilities could be more specific - listing concrete actions like implementing retry logic, exponential backoff, or request queuing would strengthen it. Overall, it effectively communicates its purpose and when to use it.

Suggestions

Add specific concrete actions like 'implement exponential backoff', 'retry failed requests', 'manage request queues' to improve specificity

Dimension	Reasoning	Score
Specificity	Names the domain (Kling AI rate limits) and mentions 'backoff strategies' as an action, but doesn't list specific concrete actions like 'implement exponential backoff', 'retry failed requests', or 'queue management'.	2 / 3
Completeness	Clearly answers both what ('Handle Kling AI rate limits with proper backoff strategies') and when ('Use when experiencing 429 errors or building high-throughput systems') with explicit trigger phrases listed.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms including 'klingai rate limit', 'kling ai 429', 'klingai throttle', 'klingai backoff', plus mentions '429 errors' and 'high-throughput systems' - terms users would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with specific product name (Kling AI) and specific error type (429/rate limits). Very unlikely to conflict with other skills due to the narrow, well-defined niche.	3 / 3
	Total	11 / 12 Passed

Reviewed

14 days ago

Table of Contents

Validation Implementation Activation

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.