logging-best-practices
From the author
Structured logging with proper levels, context, PII handling, centralized aggregation. Use for application logging, log management integration, distributed tracing, or encountering log bloat, PII exposure, missing context errors.
Install
npx skills add secondsky/claude-skills --skill logging-best-practices -a claude-code
Installs to .claude/skills/logging-best-practices/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 85
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- note-takingseb1n/awesome-ai-agent-skillsCapture, organize, and retrieve notes efficiently using structured formats, tagging, and file management for meetings, ideas, research, and daily logs. Use when the user requests note taking or provides relevant inputs for this workflow.Productivity★ 228
- Log Testing PatternsPramodDutta/qaskillsTesting logging implementations including log level verification, structured logging validation, log rotation testing, and log aggregation pipeline testing.Testing★ 240
- usage-loggingathola/claude-night-marketImplements structured usage logging and audit trails for cost and session tracking. Use when adding audit trails, usage analytics, or cost tracking to a skill.Data★ 343
- structured-logging-litemajiayu000/spellbookDesign, audit, or implement application structured logging architecture from repository evidence. Use when a user asks whether or where to add logs, how to choose or migrate a logger, how to standardize events/fields/levels/redaction, how to add HTTP access or panic logs, or why production logs cannot answer an incident question. Do not use merely to tail platform logs or to design a full metrics, tracing, SLO, and incident-management program.Design★ 288
- go-loggingcxuu/golang-skillsUse when choosing a logging approach, configuring slog, writing structured log statements, or deciding log levels in Go. Also use when setting up production logging, adding request-scoped context to logs, or migrating from log to slog, even if the user doesn't explicitly mention logging. Does not cover error handling strategy (see go-error-handling).Writing★ 181
- ploimembranedev/application-skillsPloi integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ploi data.Other★ 269
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in