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

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The body is concise and highly actionable, with executable code and specific numeric guidance throughout. Its main gaps are an implicit rather than explicit diagnostic feedback loop and an unreferenced bundle file that leaves progressive disclosure underexploited.

Suggestions

Link references/error-codes.md from the body (e.g., a 'Full error code reference' pointer) and move the detailed HTTP/task tables there so SKILL.md stays a lean overview, improving progressive_disclosure.

Convert the Diagnostic Checklist into an explicit feedback loop — e.g., 'If auth test fails, regenerate JWT then re-test' — adding validate/fix/re-verify checkpoints to raise workflow_clarity.

Add a short verification step after applying a fix (confirm task_status returns success) to close the loop on the diagnostic workflow.

DimensionReasoningScore

Conciseness

The body is lean — compact tables for HTTP codes and task failures, focused code blocks, and no padding or explanation of concepts Claude already knows (e.g., JWT, HTTP status codes); every section earns its place, so it is not the level below where unnecessary explanation lingers.

3 / 3

Actionability

Provides fully executable code (JWT encode, TokenManager, request_with_backoff, debug_request) plus copy-paste-ready specifics like ''image >= 300x300px'' and ''duration must be "5" or "10" (string, not int)'', matching the anchor for concrete, executable guidance.

3 / 3

Workflow Clarity

The Diagnostic Checklist gives an ordered sequence ('check in order: 1-7'), but it lacks explicit error-recovery feedback loops (validate → fix → re-validate), so checkpoints remain implicit rather than spelled out; it is not 3 because no validate/retry loop is articulated, and not 1 because a clear sequence does exist.

2 / 3

Progressive Disclosure

The body is well-sectioned but the bundled references/error-codes.md is never linked or signaled from SKILL.md, and the inline HTTP/task tables duplicate content that could live in that reference; this matches the anchor where references exist but are not clearly signaled and content that should be separate is inline.

2 / 3

Total

10

/

12

Passed

Description

100%

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

The description is concise, third-person, and clearly states both what the skill does and when to use it, with natural trigger phrases. It is a strong, low-conflict description with no significant weaknesses.

DimensionReasoningScore

Specificity

Names concrete actions ('Diagnose and fix') and a specific domain ('common Kling AI API errors'), matching the anchor that lists multiple specific concrete actions; it is not the level below because both verbs and the domain are explicit rather than partial.

3 / 3

Completeness

Explicitly answers both ''what'' ('Diagnose and fix common Kling AI API errors') and ''when'' ('Use when troubleshooting failed video generation or API issues'), satisfying the anchor for clearly answering both with explicit triggers.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would actually say — ''kling ai error'', ''klingai not working'', ''fix klingai'', ''klingai failed'' — giving good coverage rather than only a few relevant keywords.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Kling AI API) with distinctive triggers, making it unlikely to fire for the wrong skill; not the level below because the domain is specific rather than broadly overlapping.

3 / 3

Total

12

/

12

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.