klingai-common-errors
Execute 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'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-common-errors77
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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-structured skill description with strong trigger terms and clear when/what guidance. The main weakness is the somewhat vague capability description - 'diagnose and fix common errors' could be more specific about what types of errors or fixes are supported. The explicit trigger phrases and product-specific focus make it highly distinctive.
Suggestions
Add specific error types or fix actions (e.g., 'authentication errors, rate limits, invalid parameters, timeout issues') to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI API) and some actions ('diagnose and fix common errors', 'troubleshooting failed video generation'), but doesn't list multiple specific concrete actions like what types of errors or specific fixes are available. | 2 / 3 |
Completeness | Clearly answers both what ('Execute diagnose and fix common Kling AI API errors') and when ('Use when troubleshooting failed video generation or API issues') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'kling ai error', 'klingai not working', 'fix klingai', 'klingai failed', plus 'API issues' and 'video generation'. Includes common variations and natural phrasing. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Kling AI specifically. The explicit product name 'Kling AI' and 'klingai' variations make it highly unlikely to conflict with other API troubleshooting skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a useful error reference table and good structure, but falls short on actionability by describing solutions abstractly rather than providing executable code examples. The workflow is reasonable but lacks explicit validation checkpoints. The progressive disclosure is well-handled with appropriate separation of overview and detailed reference material.
Suggestions
Add executable code snippets for common fixes (e.g., proper Bearer token format, exponential backoff implementation) instead of just describing the solutions
Include a concrete validation command or test snippet to verify fixes work (e.g., a curl command or Python snippet to test authentication)
Remove or condense the 'Prerequisites' and 'Output' sections which add little actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with a useful error table, but includes some unnecessary sections like 'Prerequisites' and 'Output' that add little value. The overview could be trimmed. | 2 / 3 |
Actionability | Provides a helpful error reference table with causes and solutions, but lacks executable code examples. The examples section describes outcomes rather than showing actual code fixes or commands. | 2 / 3 |
Workflow Clarity | Instructions list steps in sequence (identify, match, apply, test), but validation is implicit ('test with a simple request') rather than explicit with concrete verification commands or feedback loops. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, concise error table in main file, and appropriate reference to detailed error-codes.md for comprehensive patterns. Navigation is clear and one level deep. | 3 / 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 | |
- 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.