klingai-prod-checklist
Execute pre-launch production readiness checklist for Kling AI. Use when preparing to deploy video generation to production. Trigger with phrases like 'klingai production', 'kling ai go-live', 'klingai launch checklist', 'deploy klingai'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-prod-checklist57
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 well-structured skill description with strong completeness and distinctiveness. It clearly identifies when to use the skill and provides explicit trigger phrases. The main weakness is the lack of specificity about what concrete actions the checklist involves - users don't know what tasks will be performed beyond 'execute checklist'.
Suggestions
Add 2-3 specific actions from the checklist (e.g., 'verify API credentials, validate rate limits, test error handling') to improve specificity
Consider adding what deliverables or outcomes the skill produces (e.g., 'generates readiness report, identifies blocking issues')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI production deployment) and one action (execute pre-launch production readiness checklist), but doesn't list multiple specific concrete actions like what the checklist contains or what specific tasks are performed. | 2 / 3 |
Completeness | Clearly answers both what ('Execute pre-launch production readiness checklist for Kling AI') and when ('Use when preparing to deploy video generation to production') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural trigger terms users would say: 'klingai production', 'kling ai go-live', 'klingai launch checklist', 'deploy klingai'. These are realistic phrases a user would type when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Kling AI production deployment specifically. The combination of 'Kling AI' + 'production readiness' + 'video generation' creates a distinct trigger profile unlikely to conflict with other 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 a skeleton that lacks actionable content. It provides category headings for a production checklist but no actual checklist items, specific commands, validation criteria, or concrete guidance. The structure suggests good intentions but the content fails to teach Claude how to perform any specific task.
Suggestions
Replace vague steps with specific, executable checklist items (e.g., 'Verify API key is stored in secrets manager: `vault kv get secret/klingai/api-key`')
Add concrete pass/fail criteria for each check (e.g., 'Error rate < 0.1%', 'P99 latency < 2s')
Include actual security audit items (e.g., 'Verify no credentials in code: `grep -r "KLING_API" --include="*.py"`')
Add validation checkpoints with specific commands to verify each step completed successfully
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably efficient but includes some unnecessary sections like 'Prerequisites' that state obvious requirements. The overview adds little value beyond restating the description. | 2 / 3 |
Actionability | Extremely vague - provides only high-level category names ('Audit credentials and access', 'Verify all error paths') without any concrete commands, code, specific checks, or executable guidance. This describes rather than instructs. | 1 / 3 |
Workflow Clarity | Steps are superficial labels without actual procedures. No validation checkpoints, no specific criteria for pass/fail, no feedback loops. 'Security Review: Audit credentials' tells Claude nothing about what to actually check or how. | 1 / 3 |
Progressive Disclosure | References external files for errors and examples which is good structure, but the main content is too thin to serve as a useful overview. The skill offloads all substance to other files without providing actionable quick-start content. | 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 — 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.