Logging Best Practices
boristane/agent-skillsLogging is a key part of any application. This guide shows you how to do it well. You will learn about wide events. These are single log lines that contain all the important details for one request. This helps you debug problems and understand what users are doing.
Instead of scattering many small log messages, you collect everything into one event. You include things like user IDs, cart values, and error details. This makes it much easier to find and fix issues. You can also answer new questions about your app without changing your code.
These best practices work for any service or API. They help your team keep logs consistent and useful. Anyone who writes code that logs can benefit from this simple approach.
Add Logging Best Practices skill to your workflow
Global
mkdir -p ~/.claude/skills/logging-best-practicesProject
mkdir -p .claude/skills/logging-best-practicesSource Repository
More Monitoring & Observability Claude Code Skills
Appinsights Instrumentationmicrosoft/azure-skills
Learn how to add Azure Application Insights monitoring to your web app
Azure Kustomicrosoft/azure-skills
Run fast KQL queries on Azure Data Explorer for log and telemetry analysis
Caveman Statsjuliusbrussee/caveman
See real token usage and estimated savings directly from your session log
Azure Observabilitymicrosoft/azure-skills
Track Azure app errors, performance, and infrastructure with monitoring tools
Convex Performance Auditget-convex/agent-skills
Find and fix Convex performance problems with step-by-step diagnostic guidance
Google Agents Cli Observabilitygoogle/agents-cli
Set up tracing, logging, and analytics for your ADK agents easily
Golang Observabilitysamber/cc-skills-golang
Monitor your Go services with logs metrics traces and profiling
Golang Samber Slogsamber/cc-skills-golang
Compose, sample, and route Go logs to multiple backends with ease