klingai-model-catalog
Build explore Kling AI models and their capabilities for video generation. Use when selecting models or understanding features. Trigger with phrases like 'kling ai models', 'klingai capabilities', 'kling video models', 'klingai features'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-model-catalog63
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 has strong completeness with explicit 'Use when' and 'Trigger with' clauses, and excellent distinctiveness due to brand-specific terminology. However, the specificity could be improved by listing more concrete actions beyond 'selecting models' and 'understanding features'. There also appears to be a typo ('Build explore' should likely be 'Build and explore' or just 'Explore').
Suggestions
Fix the apparent typo 'Build explore' to 'Explore' or 'Build and explore' for clarity
Add more specific concrete actions such as 'compare model versions', 'view generation parameters', or 'check model availability' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI models, video generation) and mentions some actions ('selecting models', 'understanding features'), but lacks concrete specific actions like 'generate videos', 'compare model parameters', or 'configure video settings'. | 2 / 3 |
Completeness | Clearly answers both what ('Build explore Kling AI models and their capabilities for video generation') and when ('Use when selecting models or understanding features. Trigger with phrases like...'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'kling ai models', 'klingai capabilities', 'kling video models', 'klingai features'. Good coverage of variations including the brand name with different spacing. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on 'Kling AI' brand and its video models. The brand-specific triggers ('kling ai', 'klingai') make it highly unlikely to conflict with other video or AI 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 a template or placeholder rather than actionable documentation. It claims to be a 'comprehensive guide to Kling AI's video generation models' but contains zero actual model information, no API examples, no capability comparisons, and no concrete guidance. The content describes what a skill should do rather than actually doing it.
Suggestions
Add actual model names, specifications, and capabilities (e.g., 'kling-v1: 1080p, 5-second clips, $0.05/generation')
Include executable code examples showing how to call each model via the API
Replace generic instructions with concrete decision criteria (e.g., 'Use kling-v1-turbo for <10s clips, kling-v1-pro for higher quality')
Add inline content about model tradeoffs rather than deferring everything to external references
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes unnecessary filler like 'comprehensive guide' and generic prerequisites that Claude would already understand. The instructions are vague placeholders rather than substantive content. | 2 / 3 |
Actionability | The skill provides no concrete guidance - no actual model names, no API calls, no code examples, no specific capabilities. Instructions like 'Review Available Models' and 'Compare Capabilities' are abstract descriptions rather than executable guidance. | 1 / 3 |
Workflow Clarity | The 5-step workflow is generic and could apply to any technology selection task. There are no specific validation checkpoints, no concrete decision criteria, and no actual model information to evaluate. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) and external documentation are present, but the main skill file contains almost no substantive content - it's essentially an empty shell pointing elsewhere without providing a useful overview. | 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.