klingai-debug-bundle
Execute 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'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-debug-bundle63
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is well-structured with clear 'Use when' guidance and explicit trigger phrases, making it easy for Claude to select appropriately. The main weakness is the lack of specific concrete actions - it says 'comprehensive logging and debugging' but doesn't enumerate what specific capabilities are included (e.g., request tracing, error logging, response capture).
Suggestions
Add 2-3 specific concrete actions to clarify what 'comprehensive logging and debugging' includes, e.g., 'capture API requests/responses, log error traces, configure verbosity levels'
| 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 'capture API responses', 'log error traces', or 'configure log levels'. | 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 generic debugging or logging skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a skeleton or placeholder with no actionable content. It lists what should be done at a very high level but provides zero concrete implementation details, code examples, or specific commands. The entire value is deferred to referenced files, making the skill itself nearly useless as a standalone guide.
Suggestions
Add concrete, executable code examples for at least one logging setup (e.g., Python structlog configuration with Kling AI request interceptor)
Replace abstract step labels with actual implementation details - show the specific code or commands needed for request tracing and timing
Include at least one complete, copy-paste ready example of a debug utility or logging wrapper directly in the skill
Add validation steps showing how to verify logging is working correctly (e.g., expected log output format, test commands)
| 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 implementing debugging - just abstract labels. | 1 / 3 |
Progressive Disclosure | The skill references external files for errors and examples which is appropriate, but the main content is essentially empty - it defers everything to other files without providing any substantive quick-start content in the skill itself. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 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.