Monitor and track Kling AI video generation jobs. Use when managing multiple generations or building job dashboards. Trigger with phrases like 'klingai job status', 'track klingai jobs', 'kling ai monitoring', 'klingai job queue'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-job-monitoring63
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 in specificity - while it names the domain well, it could benefit from listing more concrete actions beyond 'monitor and track'. The explicit trigger phrases and clear use-case guidance make it highly functional for skill selection.
Suggestions
Add more specific concrete actions such as 'check job status', 'list pending generations', 'view completion progress', or 'retrieve job results' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI video generation jobs) and mentions actions like 'monitor', 'track', and 'building job dashboards', but lacks comprehensive specific actions like checking status, listing pending jobs, or canceling jobs. | 2 / 3 |
Completeness | Clearly answers both what ('Monitor and track Kling AI video generation jobs') and when ('Use when managing multiple generations or building job dashboards') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural trigger terms: 'klingai job status', 'track klingai jobs', 'kling ai monitoring', 'klingai job queue' - these are phrases users would naturally say when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Kling AI job monitoring specifically, with distinct triggers mentioning 'klingai' and 'kling ai' - unlikely to conflict with other video or job monitoring 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 outline that describes what job monitoring involves without providing any actionable implementation guidance. It lacks executable code examples, specific API endpoints/payloads, polling strategies, or concrete dashboard implementation details. The content reads more like a table of contents than a functional skill.
Suggestions
Add executable code examples showing actual API calls for job status polling (e.g., GET /jobs/{id} with response handling)
Include a concrete polling implementation with rate limiting, exponential backoff, and status state machine handling
Provide a minimal working dashboard example using Rich or similar library rather than just linking to documentation
Add specific webhook payload examples and handler code if the API supports push notifications
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like the generic prerequisites and vague step descriptions that don't add value. The actual monitoring instructions are abstract rather than concrete. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete commands, and no specific examples. Steps like 'Track Job Submission' and 'Poll for Status' are vague descriptions rather than actionable instructions with actual API calls or code snippets. | 1 / 3 |
Workflow Clarity | While steps are numbered, they lack any concrete detail about what each step involves. There are no validation checkpoints, no error recovery flows, and no specific guidance on polling intervals, rate limits, or state machine handling. | 1 / 3 |
Progressive Disclosure | The skill appropriately references external files for errors and examples, but the main content is too thin - it defers almost everything to other files without providing enough substance in the overview itself to be useful standalone. | 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 | |
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.