tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-ci-integrationExecute 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'.
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 placeholder that describes what CI/CD integration should do without showing how to do it. It lacks any executable code examples (GitHub Actions YAML, Python scripts, CLI commands) and provides only abstract step descriptions. The skill defers too much to external references without giving Claude enough concrete guidance to actually implement the integration.
Suggestions
Add a complete, executable GitHub Actions workflow YAML example showing API key usage, video generation script execution, and artifact storage
Include a concrete Python script example that handles API calls, polling for completion, and error handling
Add validation checkpoints such as 'verify API key is set', 'check video generation status', and 'validate output file exists'
Provide specific commands for testing the pipeline locally before committing (e.g., act for GitHub Actions)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like the overview section and generic prerequisites. The actual instructions are high-level without much 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 scripts, no specific commands are provided. | 1 / 3 |
Workflow Clarity | Steps are listed but lack any detail on how to execute them. No validation checkpoints, no error recovery guidance, and no feedback loops for a process that involves external API calls and file generation. | 1 / 3 |
Progressive Disclosure | References to external files for errors and examples are present, but the main content is too thin - it defers almost everything to other files without providing enough actionable content in the skill itself. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
90%This description effectively communicates when to use the skill with explicit trigger phrases and a clear 'Use when' clause. However, the capability description is somewhat vague - 'Execute integrate' appears to be a grammatical error, and the description would benefit from listing specific concrete actions the skill enables beyond just 'integrate'.
Suggestions
Fix the grammatical error 'Execute integrate' and list 2-3 specific concrete actions (e.g., 'Configure GitHub Actions workflows, set up webhook triggers, manage API authentication for Kling AI video generation')
Add specific file types or configuration formats the skill handles (e.g., '.yml workflow files', 'environment variables')
| 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 (automating video content generation in build pipelines), with explicit trigger phrases provided. | 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 terms users would naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Kling AI with CI/CD automation; the explicit trigger terms like 'klingai ci' and 'kling ai github actions' make it highly 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.