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'.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is tight, highly actionable, and well-organized into clear categories with executable examples and a validation smoke test. The main weakness is that supporting reference files exist but are not surfaced or linked from SKILL.md.

Suggestions

Add a '## References' or inline links pointing to the existing bundle files (e.g., See [Automated Checklist Validator](references/automated-checklist-validator.md) and [Production Checklist](references/production-checklist.md)) so the overview routes to deeper material.

Surface references/errors.md and references/examples.md only if they add value beyond the body; examples.md currently just defers to 'code examples above', so consider enriching it or dropping it.

Move the inline full category checklists into references/production-checklist.md if it duplicates the body, keeping SKILL.md as a concise overview that links out.

Dimension	Reasoning	Score
Conciseness	A lean checklist with no over-explanation of concepts Claude already knows; the two small code snippets each earn their place, and every token is functional.	3 / 3
Actionability	Concrete, copy-paste-ready guidance throughout — specific thresholds ('30s timeout', 'duration sent as string "5"', '5-min buffer before 30-min expiry') plus executable pre-batch credit-check and smoke-test code.	3 / 3
Workflow Clarity	Though a categorized checklist rather than a multi-step process, sections are clearly organized and the Pre-Launch Smoke Test provides a validation checkpoint before declaring production-ready; per the simple-skill scoring note this qualifies for 3.	3 / 3
Progressive Disclosure	Four reference bundle files exist (automated-checklist-validator.md, errors.md, examples.md, production-checklist.md) but the SKILL.md body never links to or signals them, so navigation to supporting material is missing. Not a 1 because the body itself is well-structured; not a 3 because the available references are unlinked from the overview.	2 / 3
	Total	11 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states purpose, usage timing, and natural trigger phrases within a distinct niche. The only gap is that it summarizes capabilities at a high level rather than listing the specific checklist domains (auth, cost, monitoring, etc.).

Suggestions

Optionally name the concrete capability areas (authentication, error handling, cost controls, monitoring, security) in the description to lift specificity from 2 to 3.

Dimension	Reasoning	Score
Specificity	Names the domain ('Kling AI integrations') and a concrete function ('Production readiness checklist' used 'before going live or during deployment review'), but does not enumerate the multiple specific capabilities the checklist covers. Not a 3 because no list of concrete actions; not a 1 because domain and purpose are explicit.	2 / 3
Completeness	Explicitly answers what ('Production readiness checklist for Kling AI integrations') and when ('Use before going live or during deployment review. Trigger with phrases like ...'), satisfying both halves.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would say — 'klingai production ready', 'kling ai go live', 'klingai checklist', 'deploy klingai' — covering common variations of the intent.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Kling AI production readiness) with brand-specific triggers, making collision with unrelated skills unlikely.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.