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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill implementing-database-audit-logging79
Quality
53%
Does it follow best practices?
Impact
97%
1.03xAverage score across 6 eval scenarios
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.mdDiscovery
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 well-crafted skill description that clearly articulates specific capabilities (audit table schema generation, multiple auditing strategies), includes natural trigger terms users would actually say, and explicitly states when the skill should be activated. The description uses proper third-person voice and maintains a clear, distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'implement database audit logging', 'add audit trails', 'track database changes', and specifies options like 'trigger-based auditing, application-level logging, Change Data Capture (CDC), and parsing database logs'. Also mentions generating 'a basic audit table schema'. | 3 / 3 |
Completeness | Clearly answers both what (provides auditing options, generates audit table schema, guides strategy selection) AND when ('triggered when the user requests to...' with explicit trigger phrases). Has explicit 'Use when' equivalent with quoted trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'implement database audit logging', 'add audit trails', 'track database changes', 'audit_log'. These are realistic phrases a user would use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on database audit logging with distinct triggers like 'audit_log', 'audit trails', 'CDC'. Unlikely to conflict with general database skills or logging skills due to the specific combination of audit + database + compliance focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%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 meta-description rather than actionable guidance. It repeatedly describes what the skill does and when to use it, but never provides the actual SQL schema, trigger code, CDC configuration, or any executable implementation details. The content explains concepts Claude already understands while omitting the specific technical guidance that would make this skill useful.
Suggestions
Replace the 'How It Works' and 'When to Use This Skill' sections with actual SQL code for the audit table schema and example trigger implementations
Add concrete, copy-paste ready code examples for each auditing strategy (trigger-based, application-level, CDC) instead of describing what the skill will do
Include specific validation steps (e.g., 'Test trigger with: INSERT INTO users... then SELECT * FROM audit_log WHERE...')
Remove meta-descriptions about the skill's behavior and replace with direct instructions Claude should follow
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with unnecessary explanations of what the skill does, when to use it, and how it works. Claude doesn't need sections explaining 'How It Works' or 'When to Use This Skill' - these describe rather than instruct. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples. The skill mentions 'provides a basic SQL schema' but never actually shows it. Examples describe what the skill will do rather than providing actual implementation guidance. | 1 / 3 |
Workflow Clarity | No actual workflow steps for implementing audit logging. The numbered lists describe abstract skill behavior ('The skill will present...') rather than concrete implementation steps Claude should follow. | 1 / 3 |
Progressive Disclosure | Content is organized into sections, but it's a monolithic description without any references to detailed materials. The structure exists but contains no actionable content to organize. | 2 / 3 |
Total | 5 / 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.