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-logging

What are skills?

1.03x

Quality

53%

Does it follow best practices?

Impact

98%

1.03x

Average score across 9 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/database/database-audit-logger/skills/database-audit-logger/SKILL.md

SKILL.md

Review

Evals

Evaluation results

100%

Setting Up Audit Logging for an E-Commerce Orders Database

Audit strategy selection and schema generation

Criteria

Without context

With context

Strategy options presented

100%

All four strategies named

50%

100%

Audit table schema provided

100%

Schema captures change metadata

100%

Schema tailored to source tables

100%

Performance trade-off discussed

100%

CDC infrastructure note

100%

Strategy recommendation given

100%

Implementation notes file

100%

Without context: $0.4028 · 2m 4s · 20 turns · 21 in / 6,873 out tokens

With context: $0.5485 · 2m 19s · 28 turns · 27 in / 7,888 out tokens

85%

10%

HIPAA-Compliant Audit Trails for a Healthcare Patient Records System

Compliance-driven audit logging with retention policy

Criteria

Without context

With context

CDC recommended for compliance

Real-time rationale

100%

Retention policy defined

100%

Regulatory basis for retention

100%

Data sensitivity section

100%

Audit table schema provided

100%

Schema references source tables

100%

Access control mentioned

100%

Encryption or separation mentioned

100%

Security file exists

100%

Without context: $0.4823 · 2m 34s · 21 turns · 21 in / 9,106 out tokens

With context: $0.5744 · 2m 34s · 26 turns · 139 in / 9,019 out tokens

100%

Centralized Audit Monitoring for a Multi-Service SaaS Platform

Application-level logging with monitoring integration

Criteria

Without context

With context

Application-level strategy explained

100%

Multiple strategies contrasted

100%

Performance trade-off discussed

100%

Audit table schema provided

100%

Multi-service schema support

100%

AuditLogger implementation

100%

Application context captured

100%

Monitoring integration document

100%

Centralized view goal stated

100%

Usage example provided

100%

Without context: $0.5820 · 3m 9s · 24 turns · 25 in / 10,742 out tokens

With context: $0.6586 · 3m 12s · 28 turns · 292 in / 11,331 out tokens

100%

Tracking Down Balance Discrepancies in a Fintech Ledger

Trigger-based auditing for data debugging

Criteria

Without context

With context

Trigger-based strategy chosen

100%

Strategy comparison present

100%

Audit table schema

100%

Operation type captured

100%

Old and new values captured

100%

Timestamp column present

100%

Database user recorded

100%

Triggers on accounts table

100%

Triggers on ledger_entries table

100%

Performance impact documented

100%

SQL is executable (no placeholders)

100%

Without context: $0.3597 · 1m 51s · 18 turns · 19 in / 6,178 out tokens

With context: $0.4741 · 1m 59s · 26 turns · 59 in / 6,692 out tokens

100%

Reconstructing Database Activity After a Security Incident

Database log parsing for security monitoring

Criteria

Without context

With context

Database Logs strategy chosen

100%

Strategy options compared

100%

Log configuration parameters documented

100%

Example config values provided

100%

PII sensitivity addressed

100%

Log access control mentioned

100%

Security monitoring purpose addressed

100%

Specific tables referenced

100%

No-code-change constraint acknowledged

100%

Without context: $0.2628 · 1m 54s · 13 turns · 14 in / 5,402 out tokens

With context: $0.6264 · 3m 9s · 29 turns · 29 in / 9,753 out tokens

100%

Designing Audit Logging for a PCI-DSS Compliant Payment Platform

Audit design with retention and monitoring integration

Criteria

Without context

With context

Retention duration specified

100%

PCI-DSS cited for retention

100%

Monitoring integration described

100%

Centralized view goal stated

100%

Strategy options compared

100%

Strategy trade-offs discussed

100%

Audit table schema provided

100%

Schema captures key audit fields

100%

Source tables referenced

100%

Retention enforcement described

100%

Without context: $0.4816 · 2m 58s · 12 turns · 13 in / 11,384 out tokens

With context: $0.5663 · 2m 42s · 23 turns · 22 in / 9,725 out tokens

100%

Inventory Discrepancy Investigation

Debugging-driven audit trail selection and schema

Criteria

Without context

With context

All four strategies named

100%

Strategy recommended

100%

Trigger performance warning

100%

CDC complexity warning

100%

Audit schema provided

100%

Old value captured

100%

New value captured

100%

Timestamp captured

100%

Database user captured

100%

Schema references inventory

100%

Without context: $0.2927 · 1m 29s · 16 turns · 17 in / 4,888 out tokens

With context: $0.3683 · 1m 29s · 20 turns · 20 in / 4,645 out tokens

100%

HR Salary Data Audit System

Audit log data sensitivity and security measures

Criteria

Without context

With context

All four strategies named

62%

100%

Strategy recommended

100%

Audit schema provided

100%

Schema references compensation table

100%

Access control addressed

100%

Encryption or separation mentioned

100%

Data sensitivity section

100%

Retention policy defined

100%

Trigger performance warning

50%

100%

CDC complexity warning

100%

Operation type captured

100%

Without context: $0.3434 · 1m 54s · 18 turns · 19 in / 5,778 out tokens

With context: $0.4178 · 2m 13s · 19 turns · 52 in / 7,232 out tokens

100%

Unified Audit Strategy for a Multi-Database Platform

Cross-database audit strategy selection and comparison

Criteria

Without context

With context

All four strategies named

100%

PostgreSQL recommendation

100%

MySQL recommendation

100%

Trigger performance warning

100%

CDC complexity warning

100%

Audit schema provided

100%

Timestamp in schema

100%

Operation type in schema

100%

Strategies compared

100%

Performance-based selection reasoning

100%

Without context: $0.3785 · 2m 7s · 18 turns · 19 in / 6,783 out tokens

With context: $0.5070 · 2m 13s · 28 turns · 688 in / 7,020 out tokens

Evaluated: 5 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Setting Up Audit Logging for an E-Commerce Orders Database HIPAA-Compliant Audit Trails for a Healthcare Patient Records System Centralized Audit Monitoring for a Multi-Service SaaS Platform Tracking Down Balance Discrepancies in a Fintech Ledger Reconstructing Database Activity After a Security Incident Designing Audit Logging for a PCI-DSS Compliant Payment Platform Inventory Discrepancy Investigation HR Salary Data Audit System Unified Audit Strategy for a Multi-Database Platform

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.