tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-sdk-patternsImplement common SDK patterns for Kling AI integration. Use when building production applications with Kling AI. Trigger with phrases like 'klingai sdk', 'kling ai client', 'klingai patterns', 'kling ai best practices'.
Validation
81%| 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 | |
Implementation
22%This skill is essentially a skeleton or outline rather than actionable guidance. It describes what should be done at a high level but provides no concrete code, specific patterns, or executable examples. The content fails to teach Claude anything it doesn't already know about SDK patterns - it merely lists concepts without implementation details.
Suggestions
Add concrete, executable code examples for client initialization, showing actual Kling AI SDK usage with proper imports and configuration
Include specific error handling code with actual exception types and retry logic implementation (e.g., exponential backoff pattern)
Provide a complete async job polling example with timeout handling and status checking
Replace abstract instruction steps with actual implementation code or at minimum pseudocode that shows the specific Kling AI API calls and patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like 'Understanding of async programming concepts' as a prerequisite (Claude knows this) and vague section headers. The actual instructions are abstract placeholders rather than concrete content. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, or executable examples. The 'Instructions' section lists abstract steps like 'Build a reusable client class' without any actual implementation, code snippets, or specific guidance on how to accomplish these tasks. | 1 / 3 |
Workflow Clarity | While steps are numbered, they are vague descriptions rather than actionable sequences. There are no validation checkpoints, no feedback loops for error recovery, and no concrete guidance on what constitutes success at each step. | 1 / 3 |
Progressive Disclosure | The skill does reference external files for errors and examples, which is good structure. However, the main content is so thin that it's unclear what value this file provides beyond being a pointer to other files. The references use template variables ({baseDir}) which is appropriate. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
90%This is a well-structured description with strong trigger terms and clear 'when to use' guidance. The main weakness is the lack of specific concrete actions - 'common SDK patterns' is somewhat vague and doesn't tell Claude exactly what capabilities this skill provides (e.g., authentication, error handling, request building).
Suggestions
Replace 'common SDK patterns' with specific actions like 'handle authentication, manage rate limits, structure API requests, process responses'
Add examples of what 'production applications' means in this context (e.g., 'video generation apps', 'image processing pipelines')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI SDK/integration) and mentions 'common SDK patterns' and 'production applications', but doesn't list specific concrete actions like 'authenticate requests', 'handle rate limits', or 'manage API responses'. | 2 / 3 |
Completeness | Clearly answers both what ('Implement common SDK patterns for Kling AI integration') and when ('Use when building production applications with Kling AI. Trigger with phrases like...'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'klingai sdk', 'kling ai client', 'klingai patterns', 'kling ai best practices'. Good coverage of variations including spacing differences. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Kling AI SDK specifically. The explicit product name 'Kling AI' and SDK-focused triggers make it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Reviewed
Table of Contents
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.