Generate videos from text prompts with Kling AI. Use when creating videos from descriptions or learning prompt techniques. Trigger with phrases like 'kling ai text to video', 'klingai prompt', 'generate video from text', 'text2video kling'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-text-to-video67
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 is a well-structured skill description with excellent trigger term coverage and clear completeness. The main weakness is the specificity of capabilities - it could benefit from listing more concrete actions beyond just 'generate videos' such as specific features, video styles, or output options that Kling AI supports.
Suggestions
Add more specific capabilities like video duration options, style controls, or resolution settings (e.g., 'Generate videos up to 10 seconds, control camera movement, adjust aspect ratios')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI video generation) and mentions 'text prompts' and 'learning prompt techniques', but doesn't list multiple concrete actions like specific video types, editing capabilities, or output formats. | 2 / 3 |
Completeness | Clearly answers both what ('Generate videos from text prompts with Kling AI') and when ('Use when creating videos from descriptions or learning prompt techniques') with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'kling ai text to video', 'klingai prompt', 'generate video from text', 'text2video kling' - these are realistic phrases users would actually type when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific product name 'Kling AI' and unique trigger terms like 'klingai prompt' and 'text2video kling' that are unlikely to conflict with other video or AI skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good structural organization and progressive disclosure but critically lacks actionable content. It reads more like a table of contents than executable guidance—there's no actual code, API call examples, or concrete prompt techniques. The workflow is too abstract to be useful without the referenced example files doing all the heavy lifting.
Suggestions
Add executable code examples showing actual API calls for text-to-video generation (e.g., Python requests to the Kling AI endpoint with proper headers and payload)
Include 2-3 concrete prompt examples with expected outputs, demonstrating the prompt engineering techniques mentioned in the overview
Add validation/retry logic in the workflow for handling common failure cases like rate limits or content policy rejections
Remove generic prerequisites like 'Understanding of video generation concepts' that don't provide actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like 'Understanding of video generation concepts' as a prerequisite and generic phrases like 'Write a descriptive, clear prompt' that don't add value for Claude. | 2 / 3 |
Actionability | The skill provides only vague, abstract guidance with no concrete code, API calls, or executable examples. Steps like 'Craft Your Prompt' and 'Submit Request' describe rather than instruct, with no actual implementation shown. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack any validation checkpoints or error recovery guidance. The workflow mentions 'Monitor Progress' but doesn't explain how to handle failures or retry logic. | 2 / 3 |
Progressive Disclosure | Good structure with clear overview, well-signaled one-level-deep references to errors.md and examples.md, and external resource links. Content is appropriately split for navigation. | 3 / 3 |
Total | 8 / 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 — 13 / 16 Passed
Validation for skill structure
| 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 | |
Table of Contents
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.