Skills Guide

Audit Logging Protocol

VerifiedSafe

Implement comprehensive audit logging to trace all critical actions. Includes backend implementation standards, database management, and verification checklist for production systems.

Download and use
Sby Skills Guide Bot
SecurityBeginner
3/8/2026
Claude CodeCursorCodex
#audit-logging#traceability#compliance#logging#supabase

Recommended for

Claude CodeCursorCodexSecurity auditSecurity engineer

Automated summary

This skill enforces that every state-changing action emits a log entry through the project's Logger service and that the database carries the expected audit columns.

Strengths

  • States a simple, checkable rule: every POST, PUT, and DELETE call must produce a log entry
  • Requires concrete minimum fields (userId, action, resourceId, metadata) that make logs actually useful
  • Ships a verification checklist that can be applied before closing out an endpoint
  • Fits the project's own infrastructure (in-house Logger service plus Supabase tables with created_at, updated_at, created_by)

Limitations

  • Does not cover log retention, rotation, or tamper protection
  • Assumes a Logger service and/or an audit_logs table already exist in the project
  • Ignores read-only actions and client-side events
When to use it

Use it when adding or reviewing an API endpoint or table that must leave an auditable trail for compliance or support.

When not to use it

Skip it for throwaway scripts or prototypes with no traceability requirement, where logging would only add noise.

Security analysis

Safe
Quality score78/100

The skill only uses Read, Edit, and Write tools and instructs the agent to add logging statements to code. It does not execute shell commands, network calls, destructive actions, or handle secrets. No meaningful execution risk.

No concerns found

How this analysis is made

Examples

New endpoint audit
I just added a POST /api/posts endpoint. Add audit logging to it using our Logger service and confirm it satisfies the audit checklist.
Schema audit columns
Check the Supabase tables touched by this feature and make sure they have created_at, updated_at and created_by, plus any required audit_logs inserts.
Log coverage review
Review the diff and list every state-changing API call that is missing a Logger entry, then patch them.

name: audit_logging description: Ensure every critical action is logged (vital for UAG/Trust Room). allowed-tools: Read, Edit, Write

Audit Logging Protocol

1. Principles

  • No Invisible Actions: Every state-changing API call (POST, PUT, DELETE) must produce a log entry.
  • Traceability: Logs must include userId, action, resourceId, and metadata.

2. Implementation Standards

  • Backend (API):
    • Use the project's standard Logger service (e.g., src/services/logger.ts or similar).
    • Example: 
      await Logger.info({
  event: 'POST_CREATED',
  userId: user.id,
  metadata: { postId: newPost.id }
});
  • Database (Supabase):
    • Ensure tables have created_at, updated_at, and created_by columns.
    • Check if specific Audit Table inserts are required (e.g. audit_logs table).

3. Verification Checklist

  • [ ] Does the new API endpoint call Logger?
  • [ ] Are logs visible in Supabase/Dashboards?
  • [ ] Is the log level appropriate (Info vs Error)?
  • [ ] Does the log contain enough context to debug issues later?

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/audit-logging-protocol-mmh8qqr4/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/audit-logging-protocol-mmh8qqr4' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/audit-logging-protocol-mmh8qqr4/download' --output '.skill-downloads/audit-logging-protocol-mmh8qqr4/SKILL.md.part' && mv '.skill-downloads/audit-logging-protocol-mmh8qqr4/SKILL.md.part' '.skill-downloads/audit-logging-protocol-mmh8qqr4/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Edit, Write

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/audit-logging-protocol-mmh8qqr4/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

DeFi AMM Security

Security

Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, donation attacks, oracle manipulation, slippage, and integer math.

Claude CodeCursorCodexadvancedSafe 243,989
Skills Guide Bot

Semgrep Rule Creator

Security

Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Includes test-first methodology, taint mode support, and validation steps. Helps when building targeted static analysis detections.

Claude CodeintermediateSafe 21,468
Skills Guide Bot

Dev Toolbar Review Guide

Security

Safety rules for the dev toolbar, PostHog client, and feature flags. Use when reviewing changes to dev-tools and related files, covering environment guards, override cookies, and SSE stream safety.

Claude CodeCursorCodexintermediateSafe 108,624
Skills Guide Bot