CtrlK
BlogDocsLog inGet started
Tessl Logo

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'.

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, highly actionable debugging reference built from tables and executable code with a clear diagnostic checklist. Its main weakness is progressive disclosure: an error-codes.md bundle file exists but is neither linked nor used to offload the inlined error tables.

Suggestions

Link references/error-codes.md from the body (e.g., a "Full error code reference" pointer) and move the bulk of the HTTP/task error tables into it, keeping only the most common codes inline in SKILL.md.

Add an explicit feedback loop to the Diagnostic Checklist (e.g., "If auth check fails, regenerate JWT then re-test before proceeding") to lift workflow clarity toward 5.

Confirm whether the inline HTTP error table and references/error-codes.md are meant to overlap; if so, deduplicate so SKILL.md points to the reference rather than duplicating it.

DimensionReasoningScore

Conciseness

The body is lean tables and executable code with no padding or explanations of concepts Claude already knows (e.g., no "what is a JWT" preamble), so every token earns its place per the score-5 anchor.

5 / 5

Actionability

Copy-paste-ready code for JWT TokenManager, exponential backoff, and debug logging plus concrete thresholds ("image >= 300x300px", "duration must be \"5\" or \"10\"") cover the common cases, matching the score-5 anchor.

5 / 5

Workflow Clarity

The "Diagnostic Checklist" provides a clear ordered 1-7 sequence and the backoff code embeds retry feedback, but the main diagnostic flow lacks an explicit validate-then-fix-then-retry loop, so it sits at score 4 rather than 5.

4 / 5

Progressive Disclosure

A bundle file references/error-codes.md exists but is never linked from the body, while the HTTP error-code table is inlined, so content that belongs in the separate file is duplicated and the reference is not signaled, matching the score-3 anchor.

3 / 5

Total

17

/

20

Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that cleanly states what the skill does and when to use it with concrete, natural trigger phrases. The only modest dimension is specificity, since it names just two actions rather than enumerating several.

DimensionReasoningScore

Specificity

Quotes "Diagnose and fix common Kling AI API errors" name the domain plus two concrete actions (diagnose, fix), matching the score-3 anchor of 1-2 concrete actions without comprehensive coverage; not a 4 because only two actions are listed rather than several.

3 / 5

Completeness

Explicitly answers what ("Diagnose and fix common Kling AI API errors") and when ("Use when troubleshooting failed video generation or API issues") with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Trigger phrases "kling ai error", "klingai not working", "fix klingai", "klingai failed" are natural user utterances with good synonym coverage; file extensions are not applicable to an API-debugging skill, so this meets the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

The Kling AI API error niche with brand-specific triggers ("klingai not working", "fix klingai") is clearly distinct with minimal conflict risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.