logging-best-practices · ncklrs — Claude Code skill: what it does & install
logging-best-practices guides AI coding agents to implement wide request events, structured records, and tail sampling instead of scattered debug strings.
no license 148 installs ★ 54 updated 2026-02-26
npx skills add ncklrs/startup-os-skills --skill logging-best-practices -a claude-codeWhat logging-best-practices does
This skill guides coding assistants to replace fragmented console messages with rich per-request events. Based on Boris Tane's observability philosophy, the pattern collects contextual attributes during execution and writes out a single structured payload when processing completes.
Guidance covers field selection for high-cardinality metadata, tail-sampling logic to keep storage costs predictable, and automated detection of noisy logging habits during code reviews. It pushes designs toward events with 40 or more descriptive attributes. That makes querying in production faster.
Adopting this model requires a request-scoped context across your stack, because wide events fail if contextual data cannot travel between functions.
What it helps with
- replace scattered debug log lines with a single wide event per request
- design high-cardinality field schemas for root-cause analysis
- configure tail sampling to keep storage costs under control
- flag legacy logging anti-patterns during pull request reviews
Example prompts for the agent
- Review the logging in
src/checkout.tsand convert it into wide events - Design structured log fields for our new auth microservice
- Set up tail sampling rules to capture all failed payment attempts
How to install logging-best-practices
1Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill logging-best-practices -a claude-code2Manually: put the files in place
~/.claude/skills/logging-best-practices/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/logging-best-practices/
1Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill logging-best-practices -a codex2Manually: put the files in place
.agents/skills/logging-best-practices/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill logging-best-practices -a cursor2Manually: put the files in place
.cursor/skills/logging-best-practices/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ncklrs/startup-os-skills skills/logging-best-practices2Manually: put the files in place
.github/skills/logging-best-practices/SKILL.md1Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill logging-best-practices -a gemini-cli2Platform CLI
gemini skills install https://github.com/ncklrs/startup-os-skills --path skills/logging-best-practicesManually: put the files in place
.devin/skills/logging-best-practices/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill logging-best-practices -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about logging-best-practices
How do I install logging-best-practices in Claude Code?
Run npx skills add ncklrs/startup-os-skills --skill logging-best-practices -a claude-code.
What does the logging-best-practices skill do?
It teaches coding agents how to emit rich, queryable events per request instead of scattered text logs across codebase functions.
What is a wide event in this skill?
It is an architecture where code gathers context into a single JSON record with dozens of fields and emits it once the transaction ends.
Similar skills
All skills for Backend and APIs →logging-best-practices by other authors comes first.