klingai-ci-integration
Execute integrate Kling AI video generation into CI/CD pipelines. Use when automating video content generation in build pipelines. Trigger with phrases like 'klingai ci', 'kling ai github actions', 'klingai automation', 'automated video generation'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-ci-integration63
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 solid skill description with excellent trigger terms and completeness. The main weakness is the specificity of capabilities - it describes the general purpose (integration) but doesn't enumerate the specific actions the skill enables. The description also has a minor grammatical issue ('Execute integrate' should be 'Integrates').
Suggestions
Add specific concrete actions like 'configure GitHub Actions workflows', 'set up API authentication', 'define video generation triggers', or 'manage output artifacts'
Fix the grammatical error: change 'Execute integrate' to 'Integrates' to use proper third person voice
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI video generation, CI/CD pipelines) and a general action (integrate, automate), but lacks specific concrete actions like 'configure workflows', 'set up triggers', or 'manage API credentials'. | 2 / 3 |
Completeness | Clearly answers both what (integrate Kling AI video generation into CI/CD pipelines) and when (explicit 'Use when' clause with 'automating video content generation in build pipelines' plus 'Trigger with phrases' section). | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural trigger terms: 'klingai ci', 'kling ai github actions', 'klingai automation', 'automated video generation' - these are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Kling AI + CI/CD pipelines with distinct triggers like 'klingai ci' and 'kling ai github actions' - unlikely to conflict with general video generation or general CI/CD skills. | 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 essentially a skeleton with no actionable content. It lists high-level steps for CI/CD integration but provides zero concrete implementation - no GitHub Actions YAML, no Python scripts, no actual commands. The skill defers to external references for both examples and error handling, leaving the main file as little more than a table of contents.
Suggestions
Add a complete, executable GitHub Actions workflow YAML example that demonstrates the full integration pattern
Include a concrete Python script for video generation that can be used in CI pipelines
Add specific commands for storing secrets (e.g., `gh secret set KLING_API_KEY`) and validating the setup
Include at least one inline example with expected output rather than deferring all examples to external files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like the overview section and generic prerequisites that Claude would already understand. The actual instructions are thin on substance. | 2 / 3 |
Actionability | The skill provides only vague, abstract steps like 'Store Secrets' and 'Create Workflow' without any concrete code, commands, or executable examples. No actual GitHub Actions YAML, no Python script, no specific commands are provided. | 1 / 3 |
Workflow Clarity | While steps are numbered, they lack any concrete detail or validation checkpoints. There's no guidance on how to verify each step succeeded, no error recovery, and the steps are essentially just category labels rather than actionable instructions. | 1 / 3 |
Progressive Disclosure | The skill does reference external files for errors and examples, which is appropriate structure. However, the main content is so thin that it's unclear what value this file provides as an overview - it defers almost everything to other files without providing a useful quick-start. | 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.