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

68%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/klingai-pack/skills/klingai-upgrade-migration/SKILL.md

Quality

Content

53%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.

The body is actionable and reasonably lean, with concrete migration code and a rollback safety net. Its main weaknesses are the absence of a numbered, validated migration workflow and the failure to reference the provided bundle files, leaving those references orphaned.

Suggestions

Add a numbered 'Upgrade Procedure' workflow with explicit validation checkpoints (e.g. run A/B comparison, verify output, then switch the model) and link to references/upgrade-procedure.md rather than only presenting topical sections.

Replace the inlined breaking-changes list and migration scripts with signaled one-level-deep links to references/breaking-changes-by-version.md and references/migration-scripts.md, and add a references section pointing to errors.md and examples.md.

Move the dated Version History and Feature Availability Matrix into a reference file (or a deprecated/old-patterns section) to avoid time-sensitive content penalizing conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable snippets and no heavy concept re-explanation, but the Version History and Feature Availability Matrix embed specific dates and version numbers outside any deprecated/old-patterns section, which the rubric flags as a conciseness penalty.	3 / 5
Actionability	Provides mostly executable, copy-paste-ready code for model_name swaps, parallel comparison, and rollback via an env var, with only minor gaps (e.g. BASE/get_headers/time are assumed rather than defined).	4 / 5
Workflow Clarity	Content is organized as topical sections rather than a sequenced migration workflow, and explicit validate-then-proceed checkpoints are absent; since upgrades are risky/batch-style operations, the missing-feedback-loop cap at 3 applies.	3 / 5
Progressive Disclosure	Five reference files exist in the bundle (breaking-changes-by-version, errors, examples, migration-scripts, upgrade-procedure) but the body never links to any of them, while breaking changes and scripts are inlined — content that belongs in separate files is inlined and references are un-signaled.	2 / 5
	Total	12 / 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.

The description is well-constructed: it states a clear purpose, gives explicit use-when guidance, and lists natural trigger phrases within a distinct niche. The only weakness is that the stated actions are somewhat generic ('migrate', 'adopt') rather than enumerating specific concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain ('Kling AI model versions') and 1-2 concrete actions ('Migrate', 'upgrading', 'adopting new features') but the actions are generic rather than a comprehensive list, matching the anchor for naming domain with 1-2 concrete actions.	3 / 5
Completeness	Explicitly 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') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Provides good natural keyword coverage with four plausible user phrases ('klingai upgrade', 'kling ai migrate', 'klingai version update', 'upgrade kling model'); a few synonyms or variations could still be missing, so it sits just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Kling AI version migration) with distinct, brand-specific triggers, giving minimal conflict risk with other 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-upgrade-migration/SKILL.md
Commit: 8585d6d

Reviewed: 13 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.