klingai-debug-bundle
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-debug-bundleExecute set up comprehensive logging and debugging for Kling AI. Use when investigating issues or monitoring requests. Trigger with phrases like 'klingai debug', 'kling ai logging', 'trace klingai', 'monitor klingai requests'.
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
22%This skill is essentially a skeleton or placeholder rather than actionable guidance. It lists what should be done without showing how to do any of it, delegating all concrete content to external references. The lack of any executable code, specific commands, or concrete examples makes it nearly useless as a standalone skill.
Suggestions
Add concrete, executable code examples for at least one logging setup (e.g., Python structlog configuration with Kling AI request interceptor)
Include a specific example of request tracing with actual code showing how to capture and log API requests/responses
Provide a minimal working debug utility function that can be copy-pasted and used immediately
Add validation steps showing how to verify the logging is working correctly (e.g., 'Run this test request and check for this log output')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like the overview section and prerequisites that Claude would already understand. The actual instructions are high-level without substance. | 2 / 3 |
Actionability | The skill provides only vague, abstract guidance with no concrete code, commands, or executable examples. Steps like 'Configure Logging' and 'Add Request Tracing' describe rather than instruct, offering no actual implementation details. | 1 / 3 |
Workflow Clarity | While steps are numbered, they are essentially a table of contents with no actual content. There are no validation checkpoints, no feedback loops, and no concrete sequence for the debugging setup process. | 1 / 3 |
Progressive Disclosure | The skill references external files for errors and examples, which is appropriate structure. However, the main content is so thin that it's essentially just pointers to other files with no substantive overview content to stand on its own. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
90%This description is strong in completeness and distinctiveness, with explicit 'Use when' guidance and clear trigger terms specific to Kling AI. The main weakness is in specificity - it describes the general purpose but doesn't enumerate the concrete actions or capabilities (e.g., what types of logs, what debugging features, what output formats).
Suggestions
Add specific concrete actions like 'capture API request/response logs', 'enable verbose tracing', 'generate debug reports' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI logging/debugging) and mentions actions like 'investigating issues' and 'monitoring requests', but lacks specific concrete actions like what logging is set up, what debugging capabilities exist, or what outputs are produced. | 2 / 3 |
Completeness | Clearly answers both what ('set up comprehensive logging and debugging for Kling AI') and when ('Use when investigating issues or monitoring requests') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural trigger terms: 'klingai debug', 'kling ai logging', 'trace klingai', 'monitor klingai requests'. These are specific phrases users would naturally say when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Kling AI debugging/logging specifically. The explicit 'klingai' and 'kling ai' terms make it highly unlikely to conflict with general debugging or logging skills. | 3 / 3 |
Total | 11 / 12 Passed |
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.