CtrlK
BlogDocsLog inGet started
Tessl Logo

klingai-content-policy

Implement content policy compliance for Kling AI prompts and outputs. Use when filtering user prompts or handling moderation. Trigger with phrases like 'klingai content policy', 'kling ai moderation', 'safe video generation', 'klingai content filter'.

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is highly actionable with several complete executable code samples and clean section organization, but it keeps everything inline while ignoring five existing bundle files, and it lacks an explicitly sequenced workflow with validation checkpoints.

Suggestions

Link the existing reference files from the body (e.g., 'See references/content-filter-implementation.md for the extended filter') so the bundle is actually navigated and inline code can be trimmed.

Add an explicit numbered workflow (1. check prompt with PromptFilter, 2. submit with the safety negative prompt, 3. on server rejection call handle_policy_rejection and revise) so the filter→submit→handle-rejection loop has clear checkpoints.

De-duplicate the DEFAULT_NEGATIVE_PROMPT logic (defined in safe_request and re-assembled in SafeKlingClient.text_to_video) and prune the most generic User-Facing Guidelines items to tighten token use.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete code and a compact reference table, but DEFAULT_NEGATIVE_PROMPT is defined and re-assembled in two separate code blocks and the User-Facing Guidelines mix in generic advice ('Rate limit prompt submissions -- prevent abuse'). It is above a 1 because it avoids explaining concepts Claude already knows, but short of a 3 due to the redundancy and generic guidance that could be tightened.

2 / 3

Actionability

It provides multiple complete, executable Python implementations (PromptFilter, safe_request, SafeKlingClient, handle_policy_rejection) that are copy-paste ready with specific methods and return shapes. It is a 3 rather than a 2 because the code is fully executable rather than pseudocode and missing no key details.

3 / 3

Workflow Clarity

A filter-then-submit-then-handle-rejection sequence is implied across sections and the filter's check() acts as a validation gate, but no explicit end-to-end workflow with sequenced checkpoints is documented. It is a 2 rather than a 1 because the sequence and a gate exist, but not a 3 because the checkpoints remain implicit rather than laid out as a clear process.

2 / 3

Progressive Disclosure

Sections are well organized, but five bundle files exist in references/ (content-filter-implementation.md, content-moderation-service.md, errors.md, examples.md, policy-violation-logger.md) and none are linked or signaled from the body, while content that could live in them is inlined. It is a 2 rather than a 1 because structure is present, but not a 3 because the provided references are neither signaled nor navigated.

2 / 3

Total

9

/

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.

The description clearly answers both what the skill does and when to invoke it, with a strong set of natural trigger phrases and a distinct, low-conflict niche. Its only weakness is mild abstraction in the leading verb and a non-comprehensive action list.

DimensionReasoningScore

Specificity

It names the Kling AI content-policy domain and a couple of actions ('filtering user prompts', 'handling moderation'), but the verb 'Implement content policy compliance' is abstract and the action list is not comprehensive. It is above a 1 because concrete domain and actions are present, but short of a 3 because it does not enumerate multiple specific concrete actions.

2 / 3

Completeness

It states what the skill does ('Implement content policy compliance for Kling AI prompts and outputs') and explicitly when to use it ('Use when filtering user prompts or handling moderation. Trigger with phrases like...'). Because an explicit 'Use when...' clause with triggers is present, it is a 3 and not capped at 2.

3 / 3

Trigger Term Quality

It lists four natural trigger phrases a user would plausibly say ('klingai content policy', 'kling ai moderation', 'safe video generation', 'klingai content filter'), giving good coverage. It is a 3 rather than a 2 because multiple realistic natural-language triggers are explicitly enumerated.

3 / 3

Distinctiveness Conflict Risk

The Kling AI content-policy niche is narrow and the triggers ('klingai content policy', 'kling ai moderation') are distinct, making conflict with other skills unlikely. It is a 3 rather than a 2 because the niche and triggers are clearly distinguishable.

3 / 3

Total

11

/

12

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.