klingai-rate-limits
Handle Kling AI API rate limits with backoff and queuing strategies. Use when hitting 429 errors or planning high-volume workflows. Trigger with phrases like 'klingai rate limit', 'kling ai 429', 'klingai throttle', 'kling api limits'.
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/klingai-pack/skills/klingai-rate-limits/SKILL.mdQuality
Discovery
89%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 well-crafted description with strong trigger terms, clear 'what' and 'when' clauses, and excellent distinctiveness for its niche. The main weakness is that the capability description could be more specific about the concrete actions it teaches (e.g., exponential backoff implementation, queue management, retry headers). Overall it performs well across all dimensions.
Suggestions
Expand the capability list with more specific actions, e.g., 'Implements exponential backoff, manages request queues, parses rate limit headers, and configures retry policies for Kling AI API rate limits.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI API rate limits) and some actions (backoff and queuing strategies), but doesn't list multiple specific concrete actions like retry logic, request queuing, exponential backoff configuration, or rate limit header parsing. | 2 / 3 |
Completeness | Clearly answers both 'what' (handle Kling AI API rate limits with backoff and queuing strategies) and 'when' (when hitting 429 errors or planning high-volume workflows), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms: 'klingai rate limit', 'kling ai 429', 'klingai throttle', 'kling api limits', '429 errors', and 'high-volume workflows'. These cover multiple natural variations a user would say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (Kling AI API rate limiting) with unique trigger terms like 'klingai' and 'kling ai 429' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with executable code examples covering multiple rate-limiting strategies for Kling AI. Its main weaknesses are the lack of an integrated workflow showing how to combine these components in practice, and the somewhat verbose presentation that could benefit from splitting detailed implementations into separate reference files. The rate limit tiers table and error reference are particularly valuable additions.
Suggestions
Add a brief workflow section at the top showing the recommended decision flow: detect 429 → apply backoff → monitor usage → queue if needed, with explicit validation steps
Consider moving the full class implementations (TaskLimiter, RateLimitMonitor, RequestQueue) to a referenced file and keeping only the backoff function and usage snippets in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with useful code examples and tables, but some classes (RateLimitMonitor, RequestQueue) are somewhat verbose with docstrings and patterns that Claude could derive from minimal guidance. The rate limit tiers table and error reference are valuable and concise. | 2 / 3 |
Actionability | All code examples are fully executable, copy-paste ready Python with proper imports, complete class definitions, and usage examples. The exponential backoff, task limiter, rate monitor, and request queue are all concrete and immediately usable. | 3 / 3 |
Workflow Clarity | The skill presents individual components (backoff, limiter, monitor, queue) clearly but lacks an explicit workflow showing how to combine them or a step-by-step sequence for handling rate limits in practice. There's no validation checkpoint or decision tree for 'when you hit a 429, do X then Y then Z'. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a logical progression from simple backoff to more complex patterns. However, at ~130 lines of code-heavy content, some patterns (like the full RequestQueue or RateLimitMonitor classes) could be split into referenced files to keep the main skill leaner. The external resource links at the end are helpful. | 2 / 3 |
Total | 9 / 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
3e83543
- 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.