klingai-common-errors
Diagnose and fix common Kling AI API errors. Use when troubleshooting failed video generation or API issues. Trigger with phrases like 'kling ai error', 'klingai not working', 'fix klingai', 'klingai failed'.
91
91%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
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 solid skill description with excellent trigger terms and completeness. It clearly identifies when to use the skill and provides natural user phrases. The main weakness is that the capability description is somewhat general — listing specific error types or fix actions would strengthen it.
Suggestions
Add specific concrete actions beyond 'diagnose and fix', such as 'resolve authentication errors, handle rate limits, debug failed video generation requests, interpret error codes'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI API errors) and general actions (diagnose and fix), but doesn't list specific concrete actions like parsing error codes, handling authentication failures, or debugging rate limits. | 2 / 3 |
Completeness | Clearly answers both 'what' (diagnose and fix common Kling AI API errors) and 'when' (troubleshooting failed video generation or API issues), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would actually say: 'kling ai error', 'klingai not working', 'fix klingai', 'klingai failed', plus contextual terms like 'video generation' and 'API issues'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific product (Kling AI) with specific trigger terms that are unlikely to conflict with other skills. The niche is narrow and well-defined. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality error reference skill that is concise, actionable, and well-structured. The use of tables for error codes, wrong/correct code patterns for JWT issues, and an ordered diagnostic checklist make it immediately useful. The only minor weakness is that all content is in a single file, which is reasonable given the scope but could benefit from splitting code examples into referenced files for very large contexts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. Tables are used for error codes instead of verbose paragraphs, code examples are minimal but complete, and there's no explanation of concepts Claude already knows (no 'what is JWT' or 'what is an API' preamble). | 3 / 3 |
Actionability | Every section provides concrete, executable code or specific actionable guidance. The JWT fix shows wrong vs. correct patterns with real code, the rate limit handler is copy-paste ready, and the diagnostic checklist gives specific values (e.g., duration must be string '5' or '10', image >= 300x300px). | 3 / 3 |
Workflow Clarity | The diagnostic checklist provides a clear ordered sequence for troubleshooting with explicit checkpoints. The rate limit handler includes a feedback loop (retry with backoff). The JWT section sequences from problem identification to solution with wrong/correct patterns. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and tables, but it's a fairly long single file with no bundle files to offload detailed content. The code examples for rate limiting and debug logging could potentially be in separate referenced files, though for a standalone skill this is acceptable. External resource links are provided but internal progressive disclosure is limited. | 2 / 3 |
Total | 11 / 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
3a2d27d
- 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.