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'.
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/klingai-pack/skills/klingai-upgrade-migration/SKILL.mdQuality
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.
The description is well-structured with clear 'what' and 'when' clauses and strong, distinctive trigger terms for a niche domain. Its main weakness is the lack of specific concrete actions beyond the general concept of 'migration', which leaves the reader uncertain about what the skill actually does in practice (e.g., does it update configs, handle API changes, transform data schemas?).
Suggestions
Add 2-3 specific concrete actions the skill performs, e.g., 'Updates API endpoint configurations, handles breaking parameter changes, and validates model compatibility.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Kling AI model versions) and a general action (migrate/upgrade), but does not list specific concrete actions like 'update config files', 'remap API endpoints', or 'handle breaking changes'. It stays at a high level. | 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'. These cover common variations of how a user might phrase a migration request. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Kling AI version migration — with distinct trigger terms that are unlikely to conflict with other skills. The combination of 'kling' and 'migrate/upgrade' is highly distinctive. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable migration guidance with executable code examples and useful reference tables. Its main weaknesses are the lack of validation/verification steps in the migration workflow (e.g., confirming the new model works before decommissioning the old one) and the somewhat lengthy A/B comparison function that could be extracted. The breaking changes callout is valuable but would benefit from explicit error-handling guidance.
Suggestions
Add explicit validation steps after each migration (e.g., 'Generate a test video with the new model_name and verify the response status before updating production config')
Add error handling guidance for the breaking changes listed (e.g., what error response to expect if T2V is sent to kling-v2-1, and how to detect and recover)
Consider extracting the A/B comparison function into a referenced bundle file to keep SKILL.md focused on migration steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables and code blocks, but the version history table and feature availability matrix are quite detailed with time-sensitive version information. The parallel A/B comparison function is lengthy and could be trimmed. Some information like the version history dates may become stale. | 2 / 3 |
Actionability | Provides fully executable Python code for migration (model_name swap), A/B comparison testing, rollback via environment variables, and audio migration. Code is copy-paste ready with concrete parameter names and values. | 3 / 3 |
Workflow Clarity | Migration steps are shown but lack explicit validation checkpoints. There's no 'verify the migration worked' step after changing model_name, no error handling guidance for breaking changes (e.g., what happens if you send T2V to v2.1), and no feedback loop for catching migration issues before full rollout. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the feature availability matrix and full A/B comparison function could be split into separate reference files. Links to external resources are provided but there are no bundle files to offload detailed content. For a skill of this length (~100 lines of content), some inline detail is acceptable but the A/B comparison code bloats the main file. | 2 / 3 |
Total | 9 / 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
a04d1a2
- 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.