implementing-database-audit-logging

Process use when you need to track database changes for compliance and security monitoring. This skill implements audit logging using triggers, application-level logging, CDC, or native logs. Trigger with phrases like "implement database audit logging", "add audit trails", "track database changes", or "monitor database activity for compliance".

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/database/database-audit-logger/skills/implementing-database-audit-logging/SKILL.md

Quality

Content

62%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly actionable, copy-paste-ready audit-logging skill with strong SQL examples, but it is a monolithic wall of inline content that underutilizes its bundle files and omits the validation checkpoints the rubric expects for destructive database workflows. Promoting inline DDL and examples into the existing references/scripts and adding verify steps would push it into the top band.

Suggestions

Move the audit table DDL, trigger function, and report-query catalog into references/ files and reference them from the body so SKILL.md stays a lean overview.

Add explicit validation checkpoints after destructive/batch steps (e.g. verify triggers attached on all target tables, confirm UPDATE/DELETE grants revoked, sanity-check a test INSERT writes to audit_log).

Fix the scripts/README mismatch (it lists audit_table_creator.sh but the bundle contains audit_table_creator.py and audit-archival.sh) and actually link the real scripts from the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and earns its tokens with real DDL and trigger code, but it could be tightened — the full inline trigger function, verbose error-handling table, and lengthy worked examples add bulk that borders on over-explaining for a Claude-skilled audience.	2 / 3
Actionability	It provides complete, executable SQL (CREATE TABLE, trigger function, indexes, partitioning, report queries) and specific commands that are copy-paste ready, hitting the top anchor.	3 / 3
Workflow Clarity	The 10 instructions are clearly sequenced, but destructive/batch database operations (audit trigger creation, permission revocation, archival) lack explicit validation checkpoints, and the rubric caps workflow_clarity at 2 when feedback loops are missing for database operations.	2 / 3
Progressive Disclosure	Content is a long monolithic body with the bulk inline rather than split across the provided bundle files, and the body never references references/ or assets/; the references README is essentially empty and scripts/README lists a non-existent file, so structure is present but poorly signaled and organized.	2 / 3
	Total	9 / 12 Passed

Description

80%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is complete with strong, natural trigger phrases and a clear compliance niche, but its second-person voice and malformed 'Process use when' opener cost it specificity points and read as rough. Tightening to clean third-person ('Implements database audit logging for compliance and security monitoring') would lift it fully into the top band.

Suggestions

Rewrite in third person and fix the malformed opener, e.g. 'Implements database audit logging to track database changes for compliance and security monitoring, using triggers, application-level logging, CDC, or native logs.'

Keep the explicit trigger phrases but integrate them as a clean 'Use when...' clause rather than the awkward 'Trigger with phrases like' construction.

Dimension	Reasoning	Score
Specificity	It names multiple concrete mechanisms ("triggers, application-level logging, CDC, or native logs") which would warrant a 3, but the second-person phrasing "you need to track database changes" triggers the rubric's -1 specificity penalty, and the malformed opener "Process use when" dilutes concrete action framing.	2 / 3
Completeness	It answers both 'what' (implements audit logging via triggers/CDC/native logs) and 'when' with an explicit 'Trigger with phrases like...' clause, meeting the top anchor.	3 / 3
Trigger Term Quality	It lists natural phrases users would say — "implement database audit logging", "add audit trails", "track database changes", "monitor database activity for compliance" — giving strong coverage of likely trigger terms.	3 / 3
Distinctiveness Conflict Risk	The compliance/audit-logging niche with distinct, specific trigger phrases is clearly separable from other skills and unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/database/database-audit-logger/skills/implementing-database-audit-logging/SKILL.md
Commit: 4c47e33

Reviewed: 19 minutes ago

Table of Contents

Discovery Implementation Validation

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.