klingai-performance-tuning
Optimize Kling AI performance for speed and quality. Use when improving generation times, reducing costs, or enhancing output quality. Trigger with phrases like 'klingai performance', 'kling ai optimization', 'faster klingai', 'klingai quality settings'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-performance-tuning63
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 description has strong trigger terms and completeness with explicit 'Use when' and 'Trigger with' clauses. The main weakness is the lack of specific concrete actions - it describes goals (speed, quality, cost) rather than specific techniques or operations Claude would perform. The Kling AI focus makes it highly distinctive.
Suggestions
Add specific concrete actions like 'configure resolution settings', 'adjust frame rates', 'optimize prompt structures', or 'tune generation parameters' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI performance) and mentions general goals (speed, quality, reducing costs, generation times), but lacks specific concrete actions like 'adjust batch sizes', 'configure caching', or 'tune model parameters'. | 2 / 3 |
Completeness | Clearly answers both what (optimize Kling AI for speed and quality) and when (improving generation times, reducing costs, enhancing quality) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural trigger terms: 'klingai performance', 'kling ai optimization', 'faster klingai', 'klingai quality settings' - these are phrases users would naturally say when seeking this help. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Kling AI optimization specifically, with distinct trigger terms that are unlikely to conflict with other skills due to the specific product name. | 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 is a skeleton that lacks substantive content. It provides generic workflow steps without any concrete code, specific Kling AI settings, actual optimization techniques, or executable examples. The skill tells Claude to optimize performance without explaining how to do so.
Suggestions
Add concrete, executable code examples showing specific Kling AI optimization techniques (e.g., batch processing, caching implementations, quality/speed parameter configurations)
Replace generic steps with specific actions: instead of 'Benchmark Baseline: Measure current performance', show actual benchmarking code with timing measurements
Include specific Kling AI parameters and their performance tradeoffs (e.g., resolution settings, model selection, timeout configurations)
Add at least one complete before/after optimization example with measurable results
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like 'This skill demonstrates' and generic prerequisites. The actual actionable content is minimal for the token count used. | 2 / 3 |
Actionability | The skill provides only vague, abstract steps like 'Benchmark Baseline: Measure current performance' without any concrete code, commands, specific settings, or executable examples. It describes rather than instructs. | 1 / 3 |
Workflow Clarity | The 5 steps are generic placeholders without specific actions, validation checkpoints, or feedback loops. 'Apply Optimizations: Implement improvements' provides no actual guidance on what optimizations to apply or how. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content is so thin that it's essentially just a pointer to other files without providing a useful quick-start or overview. | 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 — 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 | |
- 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.