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'.
78
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/klingai-pack/skills/klingai-prod-checklist/SKILL.mdQuality
Discovery
62%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 and distinctiveness due to the specific 'Kling AI' domain and explicit trigger phrases. However, it critically lacks specificity about what the checklist actually covers — there are no concrete actions, checks, or outputs described. A user or Claude would know when to use this skill but not what it actually does.
Suggestions
Add specific capabilities the checklist covers, e.g., 'Validates API key configuration, rate limit settings, error handling, webhook setup, and monitoring for Kling AI integrations.'
Describe the output or actions performed, e.g., 'Generates a checklist report identifying missing configurations, security gaps, and performance concerns.'
| 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 | The 'when' is well-addressed with explicit trigger phrases and usage contexts ('before going live', 'during deployment review'). However, the 'what' is extremely weak — it only says 'production readiness checklist' without describing what the checklist actually covers or what actions the skill performs. | 2 / 3 |
Trigger Term Quality | Includes multiple natural trigger phrases like 'klingai production ready', 'kling ai go live', 'klingai checklist', 'deploy klingai' which are specific and varied. These are terms a user would plausibly say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Kling AI' as a specific product/platform and 'production readiness checklist' creates a very clear niche. The trigger terms are highly specific and unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 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-crafted production checklist that is concise, actionable, and well-organized. Its main weakness is the lack of explicit sequencing or validation gates between checklist sections—it reads as a flat list rather than a guided deployment workflow. The code examples are practical and the external references are appropriately placed.
Suggestions
Consider adding a brief sequencing note at the top indicating which sections are prerequisites for others (e.g., 'Complete Authentication and Security before running the Pre-Launch Smoke Test').
Add a validation checkpoint or gate between major sections (e.g., 'Verify authentication works in staging before proceeding to Cost Controls setup') to improve workflow clarity for multi-step deployment.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every item is a concrete checklist point with no unnecessary explanation. Claude doesn't need to be told what a secrets manager is or why exponential backoff matters—the skill just states what to do. The code examples are minimal and purposeful. | 3 / 3 |
Actionability | Checklist items are specific and concrete (e.g., '30s timeout on all HTTP calls', 'duration sent as string "5" not integer 5', 'Alert at 80% daily budget consumption'). Code examples are executable and copy-paste ready, covering pre-batch credit checks, connection pooling, and a smoke test. | 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 steps. There's no feedback loop for what to do if a checklist item fails beyond the smoke test at the end. For a production deployment checklist involving potentially destructive operations, explicit ordering and validation gates would strengthen this. | 2 / 3 |
Progressive Disclosure | The skill is well-structured with clear section headers, keeps content appropriately concise in the main file, and provides one-level-deep external references (API Reference, Content Policy, Developer Portal) at the end for deeper exploration. | 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
70e9fa4
- 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.