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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

50%

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

The body is well-structured and provides concrete, mostly-complete examples, but it falls short of fully executable guidance (undefined helpers, an API inconsistent with its own bundle), repeats value-range guidance, omits validation checkpoints, and never navigates to its existing reference files. It is a competent reference that needs tightening and bundle integration.

Suggestions

Make the code examples copy-paste ready by defining `BASE` and `get_headers()` (and the `requests` import) once, and reconcile the body's `camera_control`/`type`/`config` API with the different `camera_motion`/`camera_intensity` API in the reference bundle files so the skill is internally consistent.

Consolidate the redundant value-range guidance (inline config comments, Shot Type Quick Reference, and Intensity Guidelines overlap) and move scattered model/version numbers into a single reference or deprecated section to reduce tokens.

Add explicit validation checkpoints (e.g., verify only one config field is non-zero before posting, and check the response) and link the bundle files from the body (e.g., 'See references/cinematic-presets.md for presets') so the existing references are discoverable rather than orphaned.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and reference-style (no padded explanations of concepts Claude knows), but value-range guidance is repeated three ways (inline config comments, the Shot Type Quick Reference table, and the Intensity Guidelines table) and scattered model/version numbers ('kling-v2-6', 'v1.6+') are inline rather than in a deprecated section, so it could be tightened.	2 / 3
Actionability	The five code examples have complete, realistic request bodies, but they are not copy-paste ready: `BASE` and `get_headers()` are undefined and `requests` is not imported, and the body's `camera_control`/`type`/`config` API is inconsistent with the `camera_motion`/`camera_intensity` API used in the reference bundle files, leaving key details missing.	2 / 3
Workflow Clarity	The single-action flow (pick a shot, set one config field non-zero, POST) is present and the 'only ONE field non-zero' rule plus the error table give some guidance, but there is no explicit validation checkpoint before/after the call and no feedback loop, and the async result-retrieval step is absent, matching 'checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	The body is internally well-organized with clear sections, but the five reference bundle files are never linked or signaled from the body (the Resources section points only to external docs), and stubs like examples.md and the duplicate errors.md are orphaned, so references are present but not clearly signaled.	2 / 3
	Total	8 / 12 Passed

Description

100%

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

The description is strong: it concisely states the capability, gives an explicit 'Use when' trigger clause with multiple natural trigger phrases, and occupies a distinctive niche. It clearly answers both what the skill does and when to use it without vague fluff or voice problems.

Dimension	Reasoning	Score
Specificity	It states a concrete action ('Control camera movements in Kling AI video generation') and enumerates multiple specific concrete moves ('cinematic shots, pans, tilts, zooms, or dolly moves'), matching the 'lists multiple specific concrete actions' anchor rather than the single-domain score-2 anchor.	3 / 3
Completeness	It clearly answers both what ('Control camera movements in Kling AI video generation') and when ('Use when creating cinematic shots, pans, tilts, zooms, or dolly moves. Trigger with phrases like...'), with an explicit 'Use when'/trigger clause, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	It provides explicit natural trigger phrases a user would say ('klingai camera', 'kling ai camera motion', 'klingai cinematic', 'klingai pan zoom') plus the move names, giving good coverage of natural terms rather than only some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	The 'klingai'-prefixed niche and distinctive trigger phrases make it unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor rather than the overlapping score-2 anchor.	3 / 3
	Total	12 / 12 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
Commit: 1628598

Reviewed: 5 days 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.