CtrlK
BlogDocsLog inGet started
Tessl Logo

klingai-debug-bundle

Set up logging and debugging for Kling AI API integrations. Use when troubleshooting video generation or building observability. Trigger with phrases like 'klingai debug', 'kling ai logging', 'klingai troubleshoot', 'debug kling video generation'.

66

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 highly actionable with complete executable code, but it suffers from a monolithic inlined client class and orphaned reference files that hurt token efficiency and navigation. Adding explicit links to the existing references and surfacing a validation/checkpoint workflow would raise quality.

Suggestions

Link the six existing reference files from the body (e.g., a '## References' section pointing to request-tracing.md, logging-setup.md, errors.md, debug-utilities.md, performance-metrics.md, examples.md) so progressive disclosure is actually navigable.

Move the large KlingDebugClient class into a reference file and keep only a concise quick-start snippet in SKILL.md to improve conciseness and token efficiency.

Add an explicit debugging workflow with validation checkpoints (e.g., run diagnostic -> check auth -> inspect task -> dump log) to improve workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly dense, functional code with no concept over-explanation, but the ~90-line KlingDebugClient class inlined wholesale is heavy and could be trimmed or moved to a reference.

4 / 5

Actionability

Provides fully executable, copy-paste-ready Python and bash code covering the client, diagnostic script, and task inspector with concrete endpoints and env vars.

5 / 5

Workflow Clarity

A rough sequence exists (init client, call text_to_video, dump_log) and polling logic is shown, but there are no explicit validation checkpoints or feedback loops for the debugging workflow.

3 / 5

Progressive Disclosure

Section headers provide structure, but the bulk client code is inlined rather than split out, and none of the six existing reference files (debug-utilities.md, errors.md, examples.md, logging-setup.md, performance-metrics.md, request-tracing.md) are linked or signaled from the body.

3 / 5

Total

15

/

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.

The description is clear, distinct, and well-triggered, with explicit what/when guidance and natural trigger phrases. Its only weakness is that the stated capabilities ('logging and debugging') are somewhat generic rather than enumerating the specific diagnostic features provided.

DimensionReasoningScore

Specificity

Names the domain (Kling AI API integrations) and two concrete actions ('Set up logging and debugging'), but these are relatively high-level rather than a comprehensive list of specific capabilities.

3 / 5

Completeness

Explicitly answers both what ('Set up logging and debugging for Kling AI API integrations') and when ('Use when troubleshooting video generation or building observability') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes multiple natural trigger phrases users would actually say ('klingai debug', 'kling ai logging', 'klingai troubleshoot', 'debug kling video generation') with synonym variation.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Kling AI debugging) with distinct triggers; minimal overlap risk with 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.