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'.
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/klingai-pack/skills/klingai-audit-logging/SKILL.mdQuality
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 that clearly identifies its niche (audit logging for Kling AI), provides explicit trigger phrases, and answers both what and when. Its main weakness is that the specific capabilities could be more detailed—listing concrete actions like log format generation, compliance report creation, or specific audit fields would strengthen it.
Suggestions
Add more specific concrete actions, e.g., 'generate structured audit logs, create compliance reports, track video generation API calls, monitor usage quotas' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (audit logging for Kling AI operations) and mentions some actions (tracking API usage, preparing for audits), but doesn't list specific concrete actions like what fields are logged, what formats are supported, or what compliance standards are addressed. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement audit logging for Kling AI operations for compliance and security) and 'when' (tracking API usage, preparing for audits) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms: 'klingai audit', 'kling ai audit log', 'klingai compliance log', 'video generation audit trail'. These cover variations users would naturally say, including both the product name variations and the domain concepts (audit, compliance, trail). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of 'Kling AI' and 'audit logging'. The trigger terms are very specific to this niche and unlikely to conflict with general audit logging or general Kling AI skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid, executable audit logging code for Kling AI operations with tamper-evident chain hashing and verification. Its main weaknesses are the lack of an explicit integration workflow showing how to wire the components together, and the monolithic structure that could benefit from splitting detailed implementations into referenced files. The compliance checklist is a nice touch but doesn't compensate for the missing step-by-step usage guide.
Suggestions
Add a 'Quick Start' section at the top showing the 3-4 lines needed to wire up the AuditLogger with KlingAuditClient and start logging, before diving into implementation details.
Add an explicit workflow section: 1) Initialize logger, 2) Wrap client, 3) Use audited client for operations, 4) Verify chain integrity periodically — with validation checkpoints.
Move the report generator and verification code to separate referenced files (e.g., AUDIT_VERIFY.md, AUDIT_REPORTS.md) to keep the main skill focused on setup and core usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The code is mostly purposeful and avoids explaining basic concepts, but the overall content is quite lengthy for what it delivers. The audit report generator and some boilerplate could be tightened. The `import time` is unused. | 2 / 3 |
Actionability | Provides fully executable Python code for the audit logger, audited client wrapper, chain verification, and report generation. All code is copy-paste ready with concrete implementations rather than pseudocode. | 3 / 3 |
Workflow Clarity | The individual components are clear, but there's no explicit workflow showing how to wire them together end-to-end (e.g., instantiate base client → wrap with KlingAuditClient → verify logs). The compliance checklist is helpful but the operational sequence for using these components together is implicit rather than explicit. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear section headers, but the skill is monolithic — all code is inline rather than being split into overview + referenced files. For a skill of this length (~150 lines of code), the audit report generator and verification logic could be referenced separately. | 2 / 3 |
Total | 9 / 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 | |
- Commit
3e83543
- 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.