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

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/klingai-pack/skills/klingai-known-pitfalls/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The content is a well-organized, actionable catalog of pitfalls with tight symptom-to-fix structure and concrete code. Its main weakness is progressive disclosure: everything is inlined in SKILL.md while the bundle files are orphaned, unreferenced, and largely redundant or empty.

Suggestions

Link the bundle files from the body (e.g., a '## More pitfalls' section pointing to references/common-pitfalls.md) or remove the redundant/empty references so SKILL.md and its bundle are coherent.

Move the bulk of the per-pitfall detail into references/ and keep SKILL.md as an overview + Quick Reference table, so the main file stays scannable.

Define or stub the helper functions used in examples (check_status, generate_token, download_video) or note they are illustrative, to make the code copy-paste runnable.

DimensionReasoningScore

Conciseness

Each pitfall is tight (symptom, WRONG/RIGHT code, one-line cause) and avoids explaining concepts Claude already knows; the only redundancy is the Quick Reference table restating the fixes, keeping it at anchor 4 rather than 5.

4 / 5

Actionability

Most pitfalls give concrete WRONG/RIGHT code blocks covering the common cases, but several rely on undefined helper functions (check_status, generate_token, download_video) and pitfalls 6 and 9 have no code, so it is mostly executable with minor gaps (anchor 4, not 5).

4 / 5

Workflow Clarity

Each pitfall follows a clear symptom-to-fix sequence, and the polling and status-handling pitfalls include explicit validation/feedback patterns (timeout, failure-state checks); it is not 5 because there is no end-to-end integration workflow with checkpoints, only a catalog of independent fixes.

4 / 5

Progressive Disclosure

The body is internally well-sectioned but is a ~205-line monolith with all 10 pitfalls inlined; the provided bundle files (references/common-pitfalls.md, errors.md, examples.md) are never referenced from the body, and errors.md/examples.md are near-empty filler while common-pitfalls.md duplicates the body, matching anchor 3 (structure present, references not signaled, content that should be split is inline).

3 / 5

Total

15

/

20

Passed

Description

82%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.

The description clearly states what the skill does and when to use it, with concrete trigger phrases and a well-scoped niche. Its only weakness is that the stated actions are generic ("avoid common mistakes") rather than naming concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain ("Kling AI API") and a couple of actions ("Avoid common mistakes", "troubleshooting", "learning best practices"), but the actions are generic rather than concrete capabilities — not comprehensive, so it sits at the low end of anchor 3 rather than 4.

3 / 5

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...") with concrete trigger phrases, matching anchor 5 exactly.

5 / 5

Trigger Term Quality

Provides four natural troubleshooting phrases ("klingai pitfalls", "kling ai mistakes", "klingai gotchas", "klingai best practices") covering both spellings, but misses some natural variations like "kling api errors" or "kling ai not working", so it is good-but-not-comprehensive (anchor 4, not 5).

4 / 5

Distinctiveness Conflict Risk

Targets a clearly named niche (Kling AI API) with kling-specific trigger phrases, giving it a distinct niche with minimal overlap risk, matching anchor 5.

5 / 5

Total

17

/

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.