Agent skill

Logging Best Practices

Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics

MITAuto-check passedDevelopment

Install Logging Best Practices

skills CLI

$ npx skills add nperez0111/bookhive --skill logging-best-practices -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nperez0111/bookhive logging-best-practices --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nperez0111/bookhive.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/logging-best-practices .claude/skills/logging-best-practices && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "logging-best-practices" agent skill from https://github.com/nperez0111/bookhive/tree/main/.agents/skills/logging-best-practices into .claude/skills/logging-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-best-practices", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/nperez0111/bookhive/tree/main/.agents/skills/logging-best-practices

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add nperez0111/bookhive --skill logging-best-practices -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nperez0111/bookhive logging-best-practices --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nperez0111/bookhive.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/logging-best-practices .agents/skills/logging-best-practices && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "logging-best-practices" agent skill from https://github.com/nperez0111/bookhive/tree/main/.agents/skills/logging-best-practices into .agents/skills/logging-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-best-practices", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nperez0111/bookhive --skill logging-best-practices -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nperez0111/bookhive logging-best-practices --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nperez0111/bookhive.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/logging-best-practices .cursor/skills/logging-best-practices && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "logging-best-practices" agent skill from https://github.com/nperez0111/bookhive/tree/main/.agents/skills/logging-best-practices into .cursor/skills/logging-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-best-practices", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/nperez0111/bookhive.git --path .agents/skills/logging-best-practices

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nperez0111/bookhive --skill logging-best-practices -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nperez0111/bookhive logging-best-practices --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nperez0111/bookhive.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/logging-best-practices .gemini/skills/logging-best-practices && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "logging-best-practices" agent skill from https://github.com/nperez0111/bookhive/tree/main/.agents/skills/logging-best-practices into .gemini/skills/logging-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-best-practices", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install nperez0111/bookhive logging-best-practices

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add nperez0111/bookhive --skill logging-best-practices -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nperez0111/bookhive.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/logging-best-practices .github/skills/logging-best-practices && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "logging-best-practices" agent skill from https://github.com/nperez0111/bookhive/tree/main/.agents/skills/logging-best-practices into .github/skills/logging-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-best-practices", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nperez0111/bookhive --skill logging-best-practices -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nperez0111/bookhive logging-best-practices --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nperez0111/bookhive.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/logging-best-practices .opencode/skills/logging-best-practices && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "logging-best-practices" agent skill from https://github.com/nperez0111/bookhive/tree/main/.agents/skills/logging-best-practices into .opencode/skills/logging-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-best-practices", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: logging-best-practices
GitHub stars: 164
Used in: 2 other repos
Token cost: ~1.2k tokens
SKILL.md length: 445 words
Files: 5
Skills in repo: 1
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics

Works in 7 steps: Wide Events (CRITICAL) → High Cardinality & Dimensionality… → Business Context (CRITICAL) → …
Development work in your project
SKILL.md covers Purpose, When to Apply, Core Principles and Anti-Patterns to Avoid, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Logging Best Practices is an agent skill from nperez0111/bookhive. Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `rules/context.md`, `rules/pitfalls.md` and `rules/structure.md`).

It sits in Development. It works with Bluesky. The repository describes itself as: Track your books, share your shelves, see what others are reading. The licence is MIT.

When your agent uses it

Development work in your project

Example prompts

“/logging-best-practices”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Wide Events (CRITICAL)
High Cardinality & Dimensionality (CRITICAL)
Business Context (CRITICAL)
Environment Characteristics (CRITICAL)
Single Logger (HIGH)
Middleware Pattern (HIGH)
Structure & Consistency (HIGH)

What it can do on your machine

Read from SKILL.md and the folder at commit baa4d1b. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- loggingsucks.com
- boristane.com
- stripe.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Logging Best Practices loads about 1.2k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 445 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~32
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nperez0111/bookhive at commit baa4d1b, republished under its MIT licence (© nperez0111). 445 words, ~1,166 tokens.

Download SKILL.mdSave it as .claude/skills/logging-best-practices/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: logging-best-practices
description: Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics
license: MIT
metadata.author: boristane
metadata.version: 1.0.0

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

1. 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.

typescript

const wideEvent: Record<string, unknown> = {
  method: "POST",
  path: "/checkout",
  requestId: c.get("requestId"),
  timestamp: new Date().toISOString(),
};

try {
  const user = await getUser(c.get("userId"));
  wideEvent.user = { id: user.id, subscription: user.subscription };

  const cart = await getCart(user.id);
  wideEvent.cart = { total_cents: cart.total, item_count: cart.items.length };

  wideEvent.status_code = 200;
  wideEvent.outcome = "success";
  return c.json({ success: true });
} catch (error) {
  wideEvent.status_code = 500;
  wideEvent.outcome = "error";
  wideEvent.error = { message: error.message, type: error.name };
  throw error;
} finally {
  wideEvent.duration_ms = Date.now() - startTime;
  logger.info(wideEvent);
}

2. High Cardinality & Dimensionality (CRITICAL)

Include fields with high cardinality (user IDs, request IDs - millions of unique values) and high dimensionality (many fields per event). This enables querying by specific users and answering questions you haven't anticipated yet.

3. Business Context (CRITICAL)

Always include business context: user subscription tier, cart value, feature flags, account age. The goal is to know "a premium customer couldn't complete a $2,499 purchase" not just "checkout failed."

4. Environment Characteristics (CRITICAL)

Include environment and deployment info in every event: commit hash, service version, region, instance ID. This enables correlating issues with deployments and identifying region-specific problems.

5. Single Logger (HIGH)

Use one logger instance configured at startup and import it everywhere. This ensures consistent formatting and automatic environment context.

6. Middleware Pattern (HIGH)

Use middleware to handle wide event infrastructure (timing, status, environment, emission). Handlers should only add business context.

7. Structure & Consistency (HIGH)

Use JSON format consistently
Maintain consistent field names across services
Simplify to two log levels: info and error
Never log unstructured strings

Show full SKILL.md (169 more words)Show less

Anti-Patterns to Avoid

Scattered logs: Multiple console.log() calls per request
Multiple loggers: Different logger instances in different files
Missing environment context: No commit hash or deployment info
Missing business context: Logging technical details without user/business data
Unstructured strings: console.log('something happened') instead of structured data
Inconsistent schemas: Different field names across services

Guidelines

Wide Events (`rules/wide-events.md`)

Emit one wide event per service hop
Include all relevant context
Connect events with request ID
Emit at request completion in finally block

Context (`rules/context.md`)

Support high cardinality fields (user_id, request_id)
Include high dimensionality (many fields)
Always include business context
Always include environment characteristics (commit_hash, version, region)

Structure (`rules/structure.md`)

Use a single logger throughout the codebase
Use middleware for consistent wide events
Use JSON format
Maintain consistent schema
Simplify to info and error levels
Never log unstructured strings

Common Pitfalls (`rules/pitfalls.md`)

Avoid multiple log lines per request
Design for unknown unknowns
Always propagate request IDs across services

References:

Files

SKILL.md and 4 other files in .agents/skills/logging-best-practices of nperez0111/bookhive.

SKILL.md
rules/context.md
rules/pitfalls.md
rules/structure.md
rules/wide-events.md

Open the folder on GitHubat commit baa4d1b

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in nperez0111/bookhive, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Logging Best Practices next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Logging Best Practices compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Logging Best Practices this skillnperez0111/bookhive	164	2 repos	~1.2k	Automated safety check: Pass	MIT	5 days ago
Postdanium/lateral-thinking	321	—	~1.7k	Automated safety check: Pass	MIT	27 days ago
Scrapecreators APIScrapeCreators/social-media-research-skills	3.4k	—	~4k	Automated safety check: Notes	MIT	1 mo ago
Downstream Syncmrchantey/beet	135	—	~1.1k	Automated safety check: Pass	Apache-2.0	yesterday
Social CLIletta-ai/skills	149	—	~1.6k	Automated safety check: Notes	MIT	8 days ago
Simplified SocialLeoYeAI/openclaw-master-skills	2.2k	—	~4.8k	Automated safety check: Pass	MIT	2 mo ago

Similar skills

Post
danium/lateral-thinking
A skill your agent uses when writing a social post on a topic or a reply to someone's post — X/Twitter, LinkedIn, Bluesky, Threads — and the obvious take is not good enough.
321 GitHub stars~1.7k tokensUpdated 27 days ago
DevelopmentAuto-check passed
Scrapecreators API
ScrapeCreators/social-media-research-skills
Scrape and extract public data from 27+ social media platforms using the ScrapeCreators REST API.
3.4k GitHub stars~4k tokensUpdated 1 mo ago
Backend & APIsAuto-check: notes
Downstream Sync
mrchantey/beet
Refresh every downstream repo (beetatproto, beetconnect, beetegress, beetesp, beeteval) with beet's AGENTS.md marker block, its MIT/Apache licenses and shared config files.
135 GitHub stars~1.1k tokensUpdated yesterday
Agent WorkflowsAuto-check passed
Social CLI
letta-ai/skills
Agent-optimized CLI for Bluesky (ATProto) and X (Twitter). An agent skill from letta-ai/skills.
149 GitHub stars~1.6k tokensUpdated 8 days ago
Agent WorkflowsAuto-check: notes
Simplified Social
LeoYeAI/openclaw-master-skills
Manage your entire social media from AI — post, schedule, and analyze across Facebook, Instagram, TikTok, YouTube, LinkedIn, Pinterest, Threads, Bluesky and Google Business
2.2k GitHub stars~4.8k tokensUpdated 2 mo ago
Agent WorkflowsAuto-check passed
Vercel Composition Patterns
supabase/supabase
Official
React composition patterns that scale. An agent skill from supabase/supabase.
111k GitHub starsUsed in 58 repos~726 tokens
DevelopmentAuto-check passed

Works with

Bluesky

Questions about Logging Best Practices

What does Logging Best Practices do?

Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics. Logging Best Practices is an agent skill from nperez0111/bookhive.

When should I use Logging Best Practices?

Logging Best Practices fits situations like: development work in your project.

How do I install Logging Best Practices in Claude Code?

Run `npx skills add nperez0111/bookhive --skill logging-best-practices -a claude-code`. Or copy the skill folder (.agents/skills/logging-best-practices in nperez0111/bookhive) into .claude/skills/logging-best-practices in your project. Claude Code loads it when a task matches its description.

How do I install Logging Best Practices in Codex?

Run `npx skills add nperez0111/bookhive --skill logging-best-practices -a codex`. Or copy the skill folder (.agents/skills/logging-best-practices in nperez0111/bookhive) into .agents/skills/logging-best-practices in your project. Codex loads it when a task matches its description.

Can I use Logging Best Practices in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nperez0111/bookhive --skill logging-best-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/logging-best-practices, .gemini/skills/logging-best-practices, .github/skills/logging-best-practices and .opencode/skills/logging-best-practices in your project.

What does Logging Best Practices need to run?

SKILL.md names no scripts, command-line tools or credentials: Logging Best Practices is instructions for the agent only.

Does Logging Best Practices access the network?

SKILL.md names 3 domains. As links in the text: loggingsucks.com, boristane.com and stripe.com. This is read from the text; nothing was executed.

Is Logging Best Practices safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Logging Best Practices use?

Logging Best Practices is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Logging Best Practices use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Logging Best Practices?

Skills that share tags, products or a category with Logging Best Practices: Post (danium/lateral-thinking, 321 stars), Scrapecreators API (ScrapeCreators/social-media-research-skills, 3.4k stars), Downstream Sync (mrchantey/beet, 135 stars) and Social CLI (letta-ai/skills, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Logging Best Practices?

nperez0111 (a GitHub user) maintains it in nperez0111/bookhive, which has 164 GitHub stars. The repository was last updated on October 5, 2026.

Source: nperez0111/bookhive on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Logging Best Practices

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Logging Best Practices Skill

Purpose

When to Apply

Core Principles

1. Wide Events (CRITICAL)

2. High Cardinality & Dimensionality (CRITICAL)

3. Business Context (CRITICAL)

4. Environment Characteristics (CRITICAL)

5. Single Logger (HIGH)

6. Middleware Pattern (HIGH)

7. Structure & Consistency (HIGH)

Anti-Patterns to Avoid

Guidelines

Wide Events (rules/wide-events.md)

Context (rules/context.md)

Structure (rules/structure.md)

Common Pitfalls (rules/pitfalls.md)

Files

Used in 2 other repositories

Compare with similar skills

Similar skills

Post

Scrapecreators API

Downstream Sync

Social CLI

Simplified Social

Vercel Composition Patterns

Related

Questions about Logging Best Practices

Wide Events (`rules/wide-events.md`)

Context (`rules/context.md`)

Structure (`rules/structure.md`)

Common Pitfalls (`rules/pitfalls.md`)