klingai-upgrade-migration
Execute migrate and upgrade Kling AI SDK versions safely. Use when updating dependencies or migrating configurations. Trigger with phrases like 'klingai upgrade', 'kling ai migration', 'update klingai', 'klingai breaking changes'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-upgrade-migration57
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 well-structured skill description with strong trigger terms and clear when/what guidance. The main weakness is the somewhat generic description of capabilities - it could benefit from more specific actions like 'handles breaking changes between versions' or 'updates configuration schemas'. Overall, it should effectively distinguish itself in a skill selection scenario.
Suggestions
Add more specific concrete actions such as 'handles API deprecations', 'updates configuration schemas', or 'resolves version compatibility issues' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI SDK) and mentions actions like 'migrate', 'upgrade', 'updating dependencies', and 'migrating configurations', but lacks specific concrete actions like version-specific steps or what the migration actually entails. | 2 / 3 |
Completeness | Clearly answers both what ('Execute migrate and upgrade Kling AI SDK versions safely') and when ('Use when updating dependencies or migrating configurations') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'klingai upgrade', 'kling ai migration', 'update klingai', 'klingai breaking changes' - these are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific product name 'Kling AI SDK' and focused scope on migration/upgrade tasks. Unlikely to conflict with generic dependency or migration skills due to the specific product targeting. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a high-level outline for SDK upgrades but lacks the concrete, actionable guidance needed for Claude to actually perform migrations. The instructions are generic enough to apply to any SDK upgrade, missing Kling AI-specific commands, code patterns, or configuration examples. Critical for a migration skill, there are no validation checkpoints or rollback procedures detailed.
Suggestions
Add concrete code examples showing before/after patterns for common breaking changes in Kling AI SDK versions
Include specific commands for checking current version, updating dependencies (e.g., pip/npm commands), and validating the upgrade
Add explicit validation checkpoints with commands to verify the migration succeeded (e.g., test API calls, version checks)
Provide at least one complete migration example inline rather than deferring all examples to external files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like the 'Prerequisites' section stating obvious requirements (version control, test environment) that Claude would already know. The 'Output' section describes expected outcomes rather than providing actionable guidance. | 2 / 3 |
Actionability | The instructions are entirely abstract and vague - 'Review Changes', 'Update Dependencies', 'Update Code' provide no concrete commands, code examples, or specific steps. There's no executable guidance for actually performing a Kling AI SDK upgrade. | 1 / 3 |
Workflow Clarity | While steps are numbered, they lack any specificity or validation checkpoints. For a migration/upgrade operation (which is inherently risky), there are no concrete validation steps, no rollback procedures detailed, and no feedback loops for error recovery. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) and external documentation are present and one-level deep, but the main content is too thin - it defers almost all useful content to other files without providing a functional quick-start in the skill itself. | 2 / 3 |
Total | 6 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.