implementing-database-audit-logging
This skill helps implement database audit logging for tracking changes and ensuring compliance. It is triggered when the user requests to "implement database audit logging", "add audit trails", "track database changes", or mentions "audit_log" in relation to a database. The skill provides options for trigger-based auditing, application-level logging, Change Data Capture (CDC), and parsing database logs. It generates a basic audit table schema and guides the user through selecting the appropriate auditing strategy.
77
50%
Does it follow best practices?
Impact
97%
1.03xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-batch-20251204-000554/plugins/database/database-audit-logger/skills/database-audit-logger/SKILL.mdQuality
Discovery
100%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 strong skill description that clearly articulates what the skill does (database audit logging with multiple strategies), when to use it (explicit trigger phrases), and provides enough specificity to distinguish it from other skills. The only minor weakness is the use of 'This skill helps' which leans slightly toward a less direct voice, but it still uses third person and is otherwise well-constructed.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: implement database audit logging, trigger-based auditing, application-level logging, Change Data Capture (CDC), parsing database logs, generating audit table schema, and guiding strategy selection. | 3 / 3 |
Completeness | Clearly answers both what (provides options for trigger-based auditing, application-level logging, CDC, generates audit table schema, guides strategy selection) and when ('triggered when the user requests to implement database audit logging, add audit trails, track database changes, or mentions audit_log'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'implement database audit logging', 'add audit trails', 'track database changes', 'audit_log', 'CDC', 'Change Data Capture'. These cover common variations of how users would phrase audit-related requests. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around database audit logging specifically, with domain-specific triggers like 'audit_log', 'audit trails', 'CDC', and 'trigger-based auditing' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is almost entirely descriptive rather than instructive—it repeatedly promises to provide an audit table schema and strategy guidance but never delivers any concrete SQL, code, or specific implementation details. It reads more like a product description or README for a plugin than an actionable skill that Claude can execute. The content explains concepts Claude already understands while failing to provide the actual technical artifacts needed to implement audit logging.
Suggestions
Replace the abstract descriptions with actual executable SQL for the audit table schema (CREATE TABLE audit_log ...) and at least one complete trigger example.
Remove the 'When to Use This Skill', 'How It Works', and 'Integration' sections—these describe the skill's meta-behavior rather than providing actionable instructions Claude can follow.
Add concrete, copy-paste ready code examples for each auditing strategy (trigger-based SQL, application-level logging code, CDC configuration) instead of just naming them.
Include validation steps such as verifying the audit table was created correctly, testing that triggers fire on INSERT/UPDATE/DELETE, and checking that audit records are being captured.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what audit logging is, when to use it, what compliance means). The 'How It Works' section describes the skill's own behavior rather than providing actionable instructions. The 'When to Use This Skill' and 'Integration' sections add no value for Claude. | 1 / 3 |
Actionability | Despite mentioning a 'basic audit table schema' multiple times, the skill never actually provides one. There is no executable SQL, no trigger code, no concrete commands—only vague descriptions of what the skill 'will do.' The examples describe outcomes rather than providing copy-paste ready implementations. | 1 / 3 |
Workflow Clarity | The workflow steps are abstract meta-descriptions ('Present audit strategies', 'Guide the user') rather than concrete sequenced instructions. There are no validation checkpoints, no error handling, and no feedback loops for what is inherently a multi-step database operation. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block with no references to supporting files, no linked resources, and no bundle files. All sections contain the same vague information repeated in slightly different ways, with no structured navigation to deeper content. | 1 / 3 |
Total | 4 / 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
a5f74ac
- 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.