klingai-audit-logging
Implement comprehensive audit logging for Kling AI operations. Use when tracking API usage, compliance requirements, or security audits. Trigger with phrases like 'klingai audit', 'kling ai logging', 'klingai compliance log', 'video generation audit trail'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-audit-logging63
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger terms and clear when/what guidance. The main weakness is the lack of specific concrete actions - it describes the purpose (audit logging) but not the specific capabilities (what exactly gets logged, what reports are generated, etc.).
Suggestions
Add specific concrete actions like 'record API request/response data, generate compliance reports, track video generation timestamps and costs'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI audit logging) and mentions some actions (tracking API usage, compliance requirements, security audits), but lacks specific concrete actions like 'record timestamps', 'log request/response data', or 'generate compliance reports'. | 2 / 3 |
Completeness | Clearly answers both what (implement comprehensive audit logging for Kling AI operations) and when (tracking API usage, compliance requirements, security audits) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural trigger terms: 'klingai audit', 'kling ai logging', 'klingai compliance log', 'video generation audit trail'. These are specific phrases users would naturally say when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining 'Kling AI' with 'audit logging' - unlikely to conflict with generic logging skills or other AI platform skills. The trigger terms are highly distinctive. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a skeleton structure for audit logging but lacks any concrete, actionable content. It describes what audit logging should accomplish without showing how to implement it - no code examples, no specific API calls, no actual logging implementations. The content reads more like a table of contents than a functional skill.
Suggestions
Add executable Python code showing a complete audit logger implementation with actual Kling AI API call wrapping
Include a concrete example of an audit log entry with all required fields (timestamp, user, action, checksum, etc.)
Add validation steps for verifying log integrity and a feedback loop for handling logging failures
Either inline the essential examples from references/examples.md or ensure the overview contains enough actionable content to be useful standalone
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary framing ('This skill demonstrates...') and the prerequisites section explains things Claude would know. Could be tighter. | 2 / 3 |
Actionability | Provides only vague, abstract guidance with no executable code, no concrete commands, and no specific implementation details. Steps like 'Define Events' and 'Create Logger' describe rather than instruct. | 1 / 3 |
Workflow Clarity | The 5 steps are high-level labels without any concrete sequence, validation checkpoints, or feedback loops. For security/compliance logging, missing validation is critical. No actual workflow is provided. | 1 / 3 |
Progressive Disclosure | References external files for errors and examples which is good structure, but the main content is too thin to serve as a useful overview. The skill offloads all substance to other files without providing enough actionable content here. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- 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.