klingai-known-pitfalls
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-known-pitfallsManage avoid common mistakes when using Kling AI. Use when troubleshooting issues or learning best practices to prevent problems. Trigger with phrases like 'klingai pitfalls', 'kling ai mistakes', 'klingai gotchas', 'klingai best practices'.
Activation
40%This description suffers from a grammatical error ('Manage avoid') and extreme vagueness about what the skill actually does. While it includes explicit trigger phrases and a 'Use when' clause, the lack of concrete actions or specific mistake categories makes it difficult to understand the skill's value or distinguish it from other potential Kling AI skills.
Suggestions
Fix the grammatical error and list 2-3 specific common mistakes or pitfalls the skill addresses (e.g., 'Covers prompt formatting errors, resolution mismatches, and generation timeout issues').
Add more natural trigger terms users would actually say, such as 'Kling AI not working', 'Kling AI errors', 'Kling AI tips', or 'fix Kling AI'.
Specify what concrete guidance the skill provides (e.g., 'Provides troubleshooting steps for failed generations and optimization tips for better results').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage avoid common mistakes' (grammatically incorrect) and 'prevent problems' without listing any concrete actions. It doesn't specify what mistakes, what troubleshooting steps, or what best practices are covered. | 1 / 3 |
Completeness | Has a 'Use when' clause mentioning troubleshooting and best practices, but the 'what' portion is extremely weak - it doesn't explain what specific mistakes are covered or what the skill actually teaches. The trigger guidance exists but the capability description is insufficient. | 2 / 3 |
Trigger Term Quality | Includes some relevant trigger terms ('klingai pitfalls', 'kling ai mistakes', 'klingai gotchas', 'klingai best practices'), but these are somewhat artificial phrases. Missing natural variations like 'Kling AI help', 'Kling AI errors', 'why isn't Kling working', or 'Kling AI tips'. | 2 / 3 |
Distinctiveness Conflict Risk | The Kling AI focus provides some distinctiveness, but 'troubleshooting issues' and 'best practices' are generic patterns that could overlap with other Kling AI skills or general troubleshooting skills. The specific trigger phrases help but the core description is too vague. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
22%This skill is a hollow template that fails to deliver on its promise of documenting 'common mistakes, gotchas, and pitfalls.' It contains no actual pitfalls, no concrete examples, no specific error scenarios, and no actionable guidance. The content delegates everything to external references while providing zero standalone value.
Suggestions
Add 3-5 specific, concrete pitfalls with code examples showing the wrong approach and the correct approach (e.g., 'Pitfall: Not handling rate limits' with before/after code)
Replace the generic 5-step workflow with actual troubleshooting steps tied to specific error codes or symptoms
Include at least one inline example of a common mistake and its fix rather than deferring all examples to external files
Remove filler prerequisites and replace with specific context about when this skill applies (e.g., 'Use when seeing error code X' or 'Check before implementing async generation')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes unnecessary filler like 'Basic Kling AI usage experience' and 'Desire to improve implementation' as prerequisites. The instructions are generic placeholders rather than substantive guidance. | 2 / 3 |
Actionability | The skill provides no concrete guidance whatsoever - just vague directives like 'Review Common Issues' and 'Apply Best Practices' without any actual pitfalls, code examples, or specific recommendations. It describes rather than instructs. | 1 / 3 |
Workflow Clarity | The 5-step workflow is entirely abstract ('Review', 'Apply', 'Test', 'Monitor', 'Update') with no specific actions, validation checkpoints, or concrete steps. This is a template, not a workflow. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main skill file contains almost no substantive content - it's essentially an empty shell pointing elsewhere without providing any quick-start value. | 2 / 3 |
Total | 6 / 12 Passed |
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 | |
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.