CtrlK
BlogDocsLog inGet started
Tessl Logo

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

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/klingai-pack/skills/klingai-prod-checklist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

The body is concise and actionably specific with executable code, but it lacks an ordered validation workflow for a batch/deploy-critical skill and fails to surface the four existing reference bundle files, leaving structure underused.

Suggestions

Add an explicit pre-launch sequence with validation checkpoints (e.g., run automated-checklist-validator, fix any failures, re-validate, then run the smoke test) to introduce a feedback loop and raise workflow clarity above 3.

Link the existing reference files from the body (e.g., 'See references/errors.md for the full error-handling matrix' and 'See references/automated-checklist-validator.md to run checks automatically') so progressive disclosure uses the bundle you already ship.

Move the bulk checklist into references/production-checklist.md and keep SKILL.md as a concise overview pointing to it, matching the intended one-level-deep reference structure.

DimensionReasoningScore

Conciseness

Lean terse checkbox items with no padding or explanation of concepts Claude already knows; the two short Python snippets are concrete and earn their place, with only minor illustrative excess. Not a 5 because the pre-batch and connection-pooling snippets are somewhat illustrative rather than strictly necessary.

4 / 5

Actionability

Concrete specific items (exact HTTP codes, '30s timeout', 'duration as string "5" not integer 5', backoff with jitter) plus copy-paste-ready Python and a runnable smoke test. Not a 5 because most checklist items are assertions to verify rather than runnable commands, leaving minor gaps.

4 / 5

Workflow Clarity

A categorized checklist with no explicit sequence and no validate->fix->retry feedback loops; the smoke test is a single assert with no recovery path. The rubric's batch/deploy cap (no validation in batch or destructive operations) holds this at 3 even though the simple-skill exception would otherwise apply.

3 / 5

Progressive Disclosure

Body is well-sectioned, but four reference bundle files exist (automated-checklist-validator.md, errors.md, examples.md, production-checklist.md) and none are referenced from the body, while the full checklist is inlined and the Resources section links only to external URLs. References are present but not signaled, and content that could be split is inline.

3 / 5

Total

14

/

20

Passed

Description

82%Weight 40%Scale 1-5

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 is complete and distinctive with strong trigger phrasing, but its specificity is only moderate because it describes the skill as a checklist rather than enumerating the concrete capabilities it covers.

Suggestions

List 2-3 concrete capability areas in the description (e.g., '...covering authentication, error handling, cost controls, and content safety') to raise specificity.

Add a couple more natural trigger synonyms such as 'klingai go-live', 'launch klingai', or 'ship klingai' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Production readiness checklist for Kling AI integrations') and 1-2 actions ('use before going live', 'deployment review') but does not enumerate the checklist's specific capabilities (auth, error handling, cost controls). Not a 4 because it lists no several specific concrete actions.

3 / 5

Completeness

Explicitly answers both what ('Production readiness checklist for Kling AI integrations') and when ('Use before going live or during deployment review') with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Provides four natural trigger phrases ('klingai production ready', 'kling ai go live', 'klingai checklist', 'deploy klingai') with synonym variation, but misses common synonyms like 'go-live', 'launch', or 'ship'. Good coverage but not exhaustive enough for a 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche tied specifically to Kling AI production/deployment readiness with distinct 'klingai'-prefixed triggers, giving minimal conflict risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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