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'.
86
84%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger terms and clear 'when' guidance. Its main weakness is the lack of specific concrete actions—it says 'migrate safely' but doesn't enumerate what that entails (e.g., updating configs, handling deprecated APIs, running compatibility checks). The description is concise and well-structured overall.
Suggestions
Add 2-3 specific concrete actions to improve specificity, e.g., 'Updates API endpoints, handles deprecated parameters, validates config compatibility between Kling AI model versions.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI model version migration) and a general action (migrate between versions), but doesn't list specific concrete actions like 'update config files', 'remap API endpoints', 'handle breaking changes', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (migrate between Kling AI model versions safely) and 'when' (upgrading from v1.x to v2.x, adopting new features) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes multiple natural trigger phrases users would say: 'klingai upgrade', 'kling ai migrate', 'klingai version update', 'upgrade kling model'. Also mentions version patterns like 'v1.x to v2.x' which are natural terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Kling AI version migration specifically. The trigger terms are highly distinctive and unlikely to conflict with other skills due to the 'klingai' and 'kling' prefixes. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted migration skill with strong actionability and conciseness—executable code, specific breaking changes, and quantified cost impacts. The main weaknesses are the lack of explicit validation checkpoints in the migration workflow (e.g., 'test the new model output before switching production traffic') and the inline length of reference tables and comparison code that could be split into supplementary files.
Suggestions
Add explicit validation steps to the migration workflow, e.g., 'After changing model_name, run the A/B comparison to verify output quality before switching production traffic. If quality degrades, rollback using the feature flag.'
Move the Feature Availability Matrix and Version History table to a separate REFERENCE.md file, keeping only the current migration-relevant versions inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what Kling AI is or how APIs work. Every section delivers specific, actionable information—version tables, code snippets, and breaking changes are all tightly written. | 3 / 3 |
Actionability | Provides fully executable Python code for migration steps, A/B comparison, and rollback. The breaking changes are specific and concrete (e.g., 'kling-v2-1 is I2V-only'), and cost impacts are quantified with exact credit numbers. | 3 / 3 |
Workflow Clarity | The migration steps are presented but lack explicit validation checkpoints. There's no 'verify the migration worked' step after changing model_name, no error handling guidance for failed migrations, and no feedback loop for confirming the new version produces acceptable results before committing. The A/B comparison function helps but isn't framed as a required validation step in the migration workflow. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, and links to external resources at the end. However, the feature availability matrix and version history table add significant length that could be referenced from a separate file, and the A/B comparison function is quite long inline. The skill is borderline monolithic at ~100 lines of substantive content. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
c8a915c
- Reviewed
Table of Contents
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.