klingai-upgrade-migration

Migrate between Kling AI model versions safely. Use when upgrading from v1.x to v2.x or adopting new features. Trigger with phrases like 'klingai upgrade', 'kling ai migrate', 'klingai version update', 'upgrade kling model'.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is highly actionable with executable migration code, but it inlines time-sensitive version tables and breaking-change detail that duplicate existing reference files it never links to, and lacks an explicit validated migration procedure.

Suggestions

Link the existing bundle files from the body (e.g. "For the full step-by-step procedure, see [upgrade-procedure.md](references/upgrade-procedure.md); for breaking changes per version, see [breaking-changes-by-version.md](references/breaking-changes-by-version.md)") so progressive disclosure is one level deep and signaled.

Replace the inlined Version History and Feature Availability Matrix with a brief summary pointing to breaking-changes-by-version.md, since time-sensitive version tables penalize conciseness when not in a deprecated section.

Add an explicit numbered migration workflow with validation checkpoints (run parallel A/B comparison, verify output quality, then cutover; rollback via KLING_MODEL_VERSION if validation fails) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly lean (terse code, one-sentence overview, bullet breaking changes), but the Version History and Feature Availability Matrix inline time-sensitive dates and version numbers that are not placed in a deprecated/old-patterns section and could be tightened or moved to references.	2 / 3
Actionability	Provides concrete, executable Python with specific model_name values, a complete compare_models polling loop, and an env-var rollback pattern — copy-paste ready guidance rather than abstract description.	3 / 3
Workflow Clarity	Sections imply a migration sequence and the A/B comparison includes status polling, but there is no explicit numbered migration procedure with validation checkpoints (verify output quality before cutover), so the risky migration workflow lacks explicit validation gates.	2 / 3
Progressive Disclosure	The body is organized into clear sections, but five bundle files exist (breaking-changes-by-version.md, errors.md, examples.md, migration-scripts.md, upgrade-procedure.md) and none are referenced or signaled; material that belongs in those references (version history, breaking changes, migration scripts) is inlined instead.	2 / 3
	Total	9 / 12 Passed

Description

90%

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 description that clearly states purpose and triggers in third-person voice with good natural keyword coverage. Its only weakness is specificity, naming one core action rather than enumerating multiple concrete migration actions.

Suggestions

Enumerate concrete actions to lift specificity, e.g. "Migrate between Kling AI model versions safely — swap model_name values, adapt to breaking changes, run parallel A/B comparisons, and configure rollback flags."

Dimension	Reasoning	Score
Specificity	Names the domain and core action ("Migrate between Kling AI model versions safely", "upgrading from v1.x to v2.x") but enumerates essentially one verb (migrate/upgrade) rather than multiple distinct concrete actions, and "adopting new features" is vague.	2 / 3
Completeness	Clearly answers both what ("Migrate between Kling AI model versions safely") and when ("Use when upgrading from v1.x to v2.x or adopting new features. Trigger with phrases like...") with explicit triggers.	3 / 3
Trigger Term Quality	Provides four natural trigger phrases a user would actually say ("klingai upgrade", "kling ai migrate", "klingai version update", "upgrade kling model"), giving good coverage of natural variations.	3 / 3
Distinctiveness Conflict Risk	Targets a specific product (Kling AI) with distinctive, brand-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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.