klingai-storage-integration
Execute integrate Kling AI video output with cloud storage providers. Use when storing generated videos in S3, GCS, or Azure Blob. Trigger with phrases like 'klingai storage', 'save klingai video', 'kling ai cloud storage', 'klingai s3 upload'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-storage-integration64
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 is well-structured with explicit 'Use when' and 'Trigger with' clauses that clearly define when to select this skill. The main weakness is the somewhat vague action verb 'Execute integrate' which could be more specific about what operations are supported. The trigger terms are comprehensive and the niche is clearly defined.
Suggestions
Replace 'Execute integrate' with more specific actions like 'Upload, organize, and manage Kling AI video output in cloud storage providers'
Add file format mentions if relevant (e.g., '.mp4', 'video files') to improve trigger matching
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI video output, cloud storage) and the action (integrate/store), but lacks comprehensive specific actions like 'upload', 'organize', 'manage permissions', or 'sync'. | 2 / 3 |
Completeness | Clearly answers both what (integrate Kling AI video output with cloud storage) and when (explicit 'Use when' clause with storage scenarios and 'Trigger with phrases' providing specific triggers). | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural trigger terms: 'klingai storage', 'save klingai video', 'kling ai cloud storage', 'klingai s3 upload', plus mentions specific providers (S3, GCS, Azure Blob). | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Kling AI video generation with cloud storage providers; unlikely to conflict with general cloud storage or general video skills due to the specific 'klingai' terminology. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a skeleton outline with no actionable content. It describes what should happen at a high level but provides zero executable code, no concrete examples, and no specific implementation details. The entire value is deferred to referenced files, making the main skill file ineffective as a standalone guide.
Suggestions
Add executable Python code examples for at least one cloud provider (e.g., boto3 for S3) showing the complete download-upload workflow
Include a concrete example with actual API calls: downloading a video from Kling AI response URL and uploading to S3 with metadata
Add validation checkpoints in the workflow: verify download completed, confirm upload success with ETag/checksum, validate signed URL generation
Replace abstract step descriptions with specific commands or code snippets that Claude can directly execute
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like 'This skill demonstrates' and generic prerequisites that Claude would know. The actual actionable content is minimal. | 2 / 3 |
Actionability | No executable code, no concrete commands, no specific examples. The instructions are entirely abstract ('Configure Storage', 'Download Video') with no actual implementation details or copy-paste ready code. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack any validation checkpoints. For cloud storage operations involving downloads and uploads, there should be verification steps (e.g., check file integrity, confirm upload success) which are completely absent. | 2 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main file contains almost no substantive content - it's essentially just an outline pointing elsewhere, making the skill file itself nearly useless without the referenced files. | 2 / 3 |
Total | 7 / 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.