klingai-camera-control

Control camera movements in Kling AI video generation. Use when creating cinematic shots, pans, tilts, zooms, or dolly moves. Trigger with phrases like 'klingai camera', 'kling ai camera motion', 'klingai cinematic', 'klingai pan zoom'.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, concise reference with executable examples and useful tables, undermined by a progressive-disclosure gap: the body ignores its own bundle files, which are also inconsistent with the documented API.

Suggestions

Link the relevant bundle files from the body (e.g., point to references/cinematic-presets.md for preset recipes and references/shot-sequence-generator.md for multi-shot workflows) so the reference layer is actually discoverable.

Reconcile the bundle files with SKILL.md: the bundles use a kling-v1.5 camera_motion/camera_intensity API that contradicts the body's kling-v2-6 camera_control simple-config model, which will mislead execution.

Replace or remove references/examples.md ('See code examples above') and references/errors.md, whose content duplicates the body's Error Handling table without adding value.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, relying on tight code blocks and tables; the only redundancy is the Shot Type Quick Reference overlapping the worked examples.	4 / 5
Actionability	Provides copy-paste-ready, fully executable Python calls with concrete model names, config fields, and value ranges, and the quick-reference and intensity tables cover the common shot cases.	5 / 5
Workflow Clarity	As a single-action skill (build a camera_control config and POST), the action is unambiguous and the simple-mode rule is clearly stated; it stops short of explicit validation checkpoints, but no destructive/batch cap applies.	4 / 5
Progressive Disclosure	The body is well-sectioned, but none of the five bundle files in references/ are linked or signaled from SKILL.md, and those bundles describe an inconsistent API surface (kling-v1.5 / camera_motion) versus the body's simple-config model (kling-v2-6), leaving structure present but poorly navigated.	3 / 5
	Total	16 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description that clearly states the capability, usage context, and concrete trigger phrases with strong distinctiveness. The only weak spot is specificity, where a single primary verb limits the breadth of named actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('Kling AI video generation') and concrete actions ('Control camera movements', 'creating cinematic shots, pans, tilts, zooms, or dolly moves'), but the single primary verb keeps coverage from being comprehensive rather than listing multiple distinct capabilities.	3 / 5
Completeness	Explicitly answers both 'what' (control camera movements in Kling AI video generation) and 'when' ('Use when creating cinematic shots...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural trigger phrases a user might say ('klingai camera', 'kling ai camera motion', 'klingai cinematic', 'klingai pan zoom') with good variation coverage, though a few common phrasings are absent.	4 / 5
Distinctiveness Conflict Risk	Carves a clear Kling-AI-specific camera niche with distinctive 'klingai'-prefixed triggers, presenting minimal conflict risk with unrelated skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/klingai-pack/skills/klingai-camera-control/SKILL.md
Commit: 0540a62

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.