klingai-style-transfer

Apply artistic styles and visual effects to Kling AI video generation. Use when creating stylized content or using effects API. Trigger with phrases like 'klingai style', 'kling ai effects', 'klingai artistic video', 'stylize klingai video'.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is concise and highly actionable with executable code and useful tables, but it under-specifies the multi-step async workflow (polling/status) and fails to signpost the existing references/ bundle from the main file, leaving navigation implicit.

Suggestions

Add an explicit polling/status-check step after task creation (e.g. a get_task loop with terminal-state handling) so the generation and effects workflows have a complete sequence with a validation checkpoint.

Link the references/ files from the body (e.g. under an 'Advanced' or 'Resources' section: 'Full implementation: references/style-transfer-implementation.md', 'Error handling: references/errors.md') so progressive disclosure is one level deep and clearly signaled.

Trim or repurpose references/examples.md, which currently only says 'See code examples above' and adds no navigational value.

Dimension	Reasoning	Score
Conciseness	The body is lean and token-efficient: it skips explaining what Kling AI or style transfer is and goes straight to executable code and compact tables, assuming Claude's competence rather than padding with background.	3 / 3
Actionability	It provides multiple complete, copy-paste-ready Python snippets (auth helper, text2video, effects, Kolors restyle, I2V, style-consistency template) with concrete parameters, plus ready-to-use prompt-keyword and cfg_scale tables.	3 / 3
Workflow Clarity	Steps are present but the async polling flow is only hinted at ('Poll for result as usual') rather than sequenced, and there are no validation/error-recovery checkpoints for batch generation or restyle chains, leaving checkpoints implicit per the score-2 anchor.	2 / 3
Progressive Disclosure	A references/ bundle exists (style-transfer-implementation, brand-style-consistency, style-reference-from-image, errors, examples) but the body never signals or links to it, so the overview and detail split is present on disk but not navigated from SKILL.md, matching the score-2 anchor of references present but not clearly signaled.	2 / 3
	Total	10 / 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.

A strong, concise description that names concrete capabilities, includes natural trigger phrases, and explicitly states when to use it, all scoped to a distinct Kling AI niche. Minor wrinkle: the embedded newlines and YAML quoting make it slightly awkward but the content itself is excellent.

Dimension	Reasoning	Score
Specificity	The description names multiple concrete actions ('Apply artistic styles and visual effects', 'stylized content', 'effects API') rather than vague language, matching the score-3 anchor that lists specific actions.	3 / 3
Completeness	It explicitly answers both 'what' (apply artistic styles and visual effects) and 'when' with an explicit 'Use when creating stylized content...' clause plus concrete trigger phrases, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	It includes several natural trigger phrases a user would actually say ('klingai style', 'kling ai effects', 'klingai artistic video', 'stylize klingai video'), giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	The Kling AI-specific niche and brand-name trigger phrases make it clearly distinguishable and unlikely to fire for unrelated skills, matching the score-3 anchor of a clear niche with distinct triggers.	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: 3022dd3

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.