klingai-camera-control
Manage control camera movements in Kling AI video generation. Use when creating cinematic effects, dynamic shots, or specific camera movements. Trigger with phrases like 'klingai camera', 'kling ai camera motion', 'klingai cinematic', 'klingai pan zoom'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-camera-control63
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 solid skill description with excellent trigger term coverage and clear completeness. The main weakness is the specificity of capabilities - it mentions general concepts like 'cinematic effects' and 'dynamic shots' but doesn't enumerate the specific camera movements or controls available (pan, zoom, tilt, tracking, etc.).
Suggestions
Add specific camera movement types to the capabilities list (e.g., 'pan, zoom, tilt, tracking shots, dolly movements') to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI camera movements) and mentions some actions ('cinematic effects, dynamic shots, specific camera movements'), but doesn't list comprehensive concrete actions like specific camera movement types (pan, tilt, dolly, etc.). | 2 / 3 |
Completeness | Clearly answers both what ('Manage control camera movements in Kling AI video generation') and when ('Use when creating cinematic effects, dynamic shots, or specific camera movements') with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural trigger terms: 'klingai camera', 'kling ai camera motion', 'klingai cinematic', 'klingai pan zoom' - these are specific phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche targeting specifically Kling AI camera controls with unique trigger terms like 'klingai' and 'kling ai' - unlikely to conflict with other video or camera 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 skeleton that lacks actionable content. It describes what camera control involves conceptually but provides no executable code, specific API parameters, camera motion type values, or concrete examples. The workflow steps are abstract placeholders that don't teach Claude how to actually implement camera control in Kling AI.
Suggestions
Add executable Python code showing actual Kling AI API calls with camera control parameters (e.g., pan direction, zoom intensity values, dolly speed)
Replace abstract steps with concrete actions: specify available camera motion types (pan_left, zoom_in, etc.) and their parameter ranges
Include at least one complete input/output example showing a camera control request and expected response
Add validation step showing how to verify camera movement was applied correctly before finalizing
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes unnecessary padding like 'Understanding of cinematography basics' prerequisite and vague bullet points in Output section that don't add actionable value. | 2 / 3 |
Actionability | No concrete code, API calls, or executable examples provided. Steps like 'Plan Shot' and 'Select Motion' are abstract descriptions without specific parameters, camera motion type values, or actual API usage. | 1 / 3 |
Workflow Clarity | Steps are vague placeholders without specific actions. No validation checkpoints, no concrete parameters for camera movements, and no feedback loops for reviewing/fixing camera motion issues. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content is too thin - it defers all useful content to other files while providing no actionable quick-start material. | 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.