klingai-audit-logging

Implement audit logging for Kling AI operations for compliance and security. Use when tracking API usage or preparing for audits. Trigger with phrases like 'klingai audit', 'kling ai audit log', 'klingai compliance log', 'video generation audit trail'.

Quality

75%

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-audit-logging/SKILL.md

Quality

Content

68%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 highly actionable with executable code, but it lacks an explicit validated workflow sequence and fails to connect to its own reference files, leaving the bundle poorly navigated.

Suggestions

Add a short numbered workflow (instantiate AuditLogger -> wrap client -> log operations -> verify chain -> generate report) with an explicit 'verify before reporting' checkpoint and a retry-on-mismatch feedback loop.

Replace the fully inlined implementations with concise overviews that link to references/audit-logger-implementation.md and references/audit-wrapped-client.md, keeping only minimal inline examples in SKILL.md.

Surface the existing reference files (audit-event-types.md, errors.md, examples.md) with clearly signaled one-level-deep links from the relevant sections.

Dimension	Reasoning	Score
Conciseness	The body is lean on prose and the code is executable without padding, but it inlines four full implementations that duplicate existing reference files (audit-logger-implementation.md, audit-wrapped-client.md), which is slightly more than needed inline.	4 / 5
Actionability	Provides fully executable, copy-paste-ready Python covering logging, client wrapping, chain verification, and report generation across the common cases.	5 / 5
Workflow Clarity	Components appear as labeled sections rather than a sequenced procedure, and although a verify_audit_chain function exists, there is no explicit 'validate -> fix -> retry' guidance for an integrity-sensitive, tamper-evident logging task, capping it at 3.	3 / 5
Progressive Disclosure	Five reference files exist (audit-event-types.md, audit-logger-implementation.md, audit-wrapped-client.md, errors.md, examples.md) but none are linked or signaled from the body, and examples.md merely redirects back to the inlined code, leaving references buried and content that should be separate inlined.	2 / 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 clearly states both capability and trigger conditions with natural, distinctive phrases, though its list of concrete actions is modest rather than comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain ('audit logging for Kling AI operations for compliance and security') and a couple of concrete actions ('tracking API usage', 'preparing for audits'), but does not enumerate a comprehensive list of specific operations, fitting the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	Explicitly answers both what ('Implement audit logging for Kling AI operations for compliance and security') and when ('Use when tracking API usage or preparing for audits' plus concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Provides four natural trigger phrases ('klingai audit', 'kling ai audit log', 'klingai compliance log', 'video generation audit trail') with synonym variations a user would plausibly say, matching 'good keyword coverage; a few natural terms missing'.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Kling AI audit/compliance logging) with distinctive trigger phrases, giving minimal overlap 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-audit-logging/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.