CtrlK
BlogDocsLog inGet started
Tessl Logo

klingai-known-pitfalls

Avoid common mistakes when using Kling AI API. Use when troubleshooting or learning best practices. Trigger with phrases like 'klingai pitfalls', 'kling ai mistakes', 'klingai gotchas', 'klingai best practices'.

68

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

77%

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

The content is highly actionable, with executable WRONG/CORRECT code and a clear, well-organized pitfall catalog. Its weak spots are token efficiency (a redundant summary table) and progressive disclosure (bundle files are orphaned/unused stubs never referenced from the body).

Suggestions

Remove or trim the Quick Reference table since it duplicates fixes already shown inline, or relocate it to a separate references file if a scannable summary is desired.

Link the existing bundle files from the body (e.g. 'See references/common-pitfalls.md for additional cases') and delete the empty errors.md/examples.md stubs that only say 'see above'.

Consider moving the 10 inline pitfalls into the references directory so SKILL.md stays a concise overview pointing one level deep to detailed material.

DimensionReasoningScore

Conciseness

Pitfalls are tight with no over-explanation of concepts Claude knows, but the Quick Reference table restates every fix already shown inline, adding redundant tokens that could be tightened.

2 / 3

Actionability

Most pitfalls give copy-paste-ready WRONG/CORRECT Python with specific field names and values; even the prose pitfalls (6, 9) supply concrete specifics like mutually-exclusive feature lists and the 5x credit multiplier.

3 / 3

Workflow Clarity

As a well-organized reference catalog of numbered pitfalls with consistent symptom/cause/fix structure it is clear and unambiguous; Pitfall 4 even demonstrates an explicit timeout and failure-state validation loop.

3 / 3

Progressive Disclosure

The body is well-sectioned but ~180 lines are inline, while the provided bundle files are never linked from the body and errors.md/examples.md are empty stubs that only say 'see above', so references are present but not signaled and content that could be split stays inline.

2 / 3

Total

10

/

12

Passed

Description

90%

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 clearly carves out a distinct niche (Kling AI API pitfalls) with explicit 'Use when' trigger guidance and natural trigger phrases. Its only real weakness is specificity — it states the domain and a general goal rather than enumerating concrete capabilities.

Suggestions

Replace the abstract 'Avoid common mistakes' with concrete capabilities, e.g. 'Fix 400 errors, refresh expired JWT tokens, add polling timeouts, and rehost temporary CDN videos for the Kling AI API'.

Tighten the trigger list: 'pitfalls', 'mistakes', and 'gotchas' are near-synonyms; consider adding a distinct intent like 'klingai troubleshooting' to broaden natural coverage.

DimensionReasoningScore

Specificity

Names the Kling AI API domain and a general action ('Avoid common mistakes when using Kling AI API') but does not list multiple concrete capabilities, fitting 'names domain and some actions, but not comprehensive'.

2 / 3

Completeness

Explicitly answers both what ('Avoid common mistakes when using Kling AI API') and when ('Use when troubleshooting or learning best practices. Trigger with phrases like...'), matching the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would say — 'klingai pitfalls', 'kling ai mistakes', 'klingai gotchas', 'klingai best practices' — giving good coverage of relevant terms.

3 / 3

Distinctiveness Conflict Risk

Kling AI API is a clear niche with klingai-specific triggers, making it unlikely to fire for or conflict with unrelated skills.

3 / 3

Total

11

/

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.