logging-best-practices
Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics
Install
With your agent
Install OMGSkills skill "neondatabase/mcp-server-neon:logging-best-practices" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/neondatabase/mcp-server-neon /tmp/mcp-server-neon && ln -s /tmp/mcp-server-neon/.agents/skills/logging-best-practices ~/.claude/skills/logging-best-practicesFrom README
Logging Best Practices Skill Version: 1.0.0 Purpose This skill provides guidelines for implementing effective logging in applications. It focuses on wide events (also called canonical log lines) - a pattern where you emit a single, context-rich event per request per service, enabling powerful debugging and analytics. When to Apply Apply these guidelines when: Writing or reviewing logging code Adding console.log, logger.info, or similar Designing logging strategy for new services Setting up logging infrastructure Core Principles Wide Events (CRITICAL) Emit one context-rich event per request per service. Instead of scattering log lines throughout your handler, consolidate everything into a single structured event emitted at request completion. High Cardinality & Dimensionality (CRITICAL) Include fields with high cardinality (user IDs, request IDs - millions of unique values) and high dimensionality (many fields per event).