klingai-compliance-review

Security and compliance review framework for Kling AI integrations. Use when preparing for audits or reviewing security posture. Trigger with phrases like 'klingai compliance', 'kling ai security review', 'klingai audit prep', 'video generation compliance'.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/klingai-pack/skills/klingai-compliance-review/SKILL.md

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 well-structured and actionable with concrete checklists and executable code, but it fails to connect to its own reference bundle and lacks explicit validation feedback loops for its batch compliance workflow.

Suggestions

Link the existing reference files from the body (e.g., 'For the full checker implementation, see references/compliance-checker.md') so the bundle is discoverable and the inlined code can be trimmed.

Add an explicit validate→fix→retry loop to the Automated Compliance Check workflow (run checks, review FAIL items, remediate, re-run until passing) to raise workflow clarity above 3.

Move the bulky GDPRCompliantClient and run_compliance_check implementations into references and keep only a concise representative snippet in SKILL.md to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly lean with token-efficient tables and checklists and no padding about concepts Claude already knows, though the inlined GDPRCompliantClient and run_compliance_check blocks are heavier than needed given dedicated reference files exist.	4 / 5
Actionability	Provides concrete checkbox checklists and copy-paste-ready Python (safe_log_key, GDPRCompliantClient, run_compliance_check), with only minor gaps such as the unimplemented deletion-request body.	4 / 5
Workflow Clarity	Sections imply a rough sequence (data flow → security → privacy → GDPR → automated check) but there are no explicit checkpoints, and the batch compliance check lacks a validate→fix→retry feedback loop, capping this at 3.	3 / 5
Progressive Disclosure	The body has good section headers, but it inlines large code that overlaps with dedicated reference files (compliance-checker.md, compliance-report-template.md) and never links to or signals any of the four existing reference files, leaving the bundle orphaned.	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 strong: it states what the skill does, when to use it, and provides concrete trigger phrases scoped to a distinct niche. Its only weakness is that capabilities are described at the framework level rather than as specific enumerated actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('Security and compliance review framework for Kling AI integrations') and a concrete review action, but describes a framework rather than enumerating specific actions like credential review or data-handling checks.	3 / 5
Completeness	Explicitly answers both 'what' (security and compliance review framework for Kling AI integrations) and 'when' ('Use when preparing for audits or reviewing security posture') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides natural trigger phrases ('klingai compliance', 'kling ai security review', 'klingai audit prep', 'video generation compliance') with klingai/kling ai variants, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Kling AI integrations) with distinct, product-specific trigger phrases, minimizing conflict risk with unrelated skills.	5 / 5
	Total	17 / 20 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
Path: plugins/saas-packs/klingai-pack/skills/klingai-compliance-review/SKILL.md
Commit: 8585d6d

Reviewed: 13 days 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.