klingai-prod-checklist
Production readiness checklist for Kling AI integrations. Use before going live or during deployment review. Trigger with phrases like 'klingai production ready', 'kling ai go live', 'klingai checklist', 'deploy klingai'.
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
79%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger terms, completeness, and distinctiveness due to its narrow focus on Kling AI production readiness. However, it is severely lacking in specificity—it names no concrete actions, checks, or outputs that the checklist covers, making it unclear what value the skill actually provides beyond being a generic 'checklist'.
Suggestions
Add specific concrete actions the checklist covers, e.g., 'Validates API key configuration, checks rate limit settings, verifies error handling, reviews authentication flows, and confirms webhook endpoints for Kling AI integrations.'
Specify what outputs or artifacts the skill produces, e.g., 'Generates a pass/fail report with remediation steps for each checklist item.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'production readiness checklist' but does not list any concrete actions or capabilities. It doesn't specify what the checklist covers, what checks are performed, or what outputs are produced. | 1 / 3 |
Completeness | Answers both 'what' (production readiness checklist for Kling AI integrations) and 'when' (before going live, during deployment review) with explicit trigger phrases. Both components are clearly stated. | 3 / 3 |
Trigger Term Quality | Includes multiple natural trigger phrases like 'klingai production ready', 'kling ai go live', 'klingai checklist', 'deploy klingai' that users would plausibly say. Good coverage of variations including deployment-related terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting Kling AI production deployments. The combination of 'Kling AI' + 'production readiness' + 'checklist' is very unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured production readiness checklist that is concise, actionable, and well-organized. The checklist format naturally suits the use case, with specific thresholds, concrete code examples, and clear categorization. The main weakness is the lack of explicit sequencing or validation steps between checklist phases, which would help teams work through the checklist methodically.
Suggestions
Consider adding a brief recommended order or priority grouping (e.g., 'Complete Authentication and Security sections before deploying to staging') to improve workflow clarity.
Add a validation step or gate between sections, such as 'Run smoke test after completing Error Handling and before proceeding to Production deployment' to create feedback loops.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every item in the checklist is specific and actionable with no unnecessary explanation. No concepts are over-explained—items like JWT refresh, exponential backoff, and connection pooling are stated as requirements without tutorial-style padding. | 3 / 3 |
Actionability | The checklist items are concrete and specific (e.g., '30s timeout on all HTTP calls', 'duration sent as string "5" not integer 5', 'Alert at 80% daily budget consumption'). Code examples for credit checks, connection pooling, and smoke tests are executable and copy-paste ready. | 3 / 3 |
Workflow Clarity | The checklist is well-organized into logical sections, but it's a flat checklist without explicit sequencing or validation checkpoints between phases. There's no guidance on order of operations (e.g., complete security before monitoring) or feedback loops for when checklist items fail. | 2 / 3 |
Progressive Disclosure | The skill is appropriately self-contained as a checklist with clear section headers for navigation. External references to API docs, content policy, and developer portal are provided at the end. No bundle files are needed for this type of content, and the structure is well-organized without being monolithic. | 3 / 3 |
Total | 11 / 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 | |
- Commit
a04d1a2
- 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.