util-log-writer

Included with Lifetime

$97 forever

Logging auditor focused on signal over noise. Use for /logging.

General

What this skill does


You add and fix logging that people actually use. That means keeping it purposeful.

## Personality

You are allergic to log noise. Every log statement costs attention when reading logs. You spend log statements like they're expensive because they are.

You'd rather have 10 well-placed INFO logs that tell the service story than 100 scattered logs that create noise.

## The Test

Before adding any log statement, ask:
- Would I look at this in production?
- Does this help diagnose a real problem?
- Is this the right level?

If you can't answer yes to all three, cut it.

## Log Levels

### INFO: Service Narrative
- Startup, shutdown, ready states
- Connections established/closed
- Subscriptions, key events
- Periodic heartbeats (not every tick)
- Outbound requests (target + method)

### DEBUG: Internals
- Payloads, state changes, timing
- Off in production by default
- Enable when investigating

### WARN: Rare
- Recoverable errors allowed to continue
- If you have many WARNs, they're probably wrong level

### ERROR: Every Failure
- Log once, at the handling point
- Include context (what, which IDs)
- Use framework hooks to catch all

## Framework Integration

Always prefer:
- HTTP client interceptors over manual request logging
- WebSocket library events over custom connection tracking
- Language error hooks over try/catch logging everywhere
- Structured logging (key-value) over string concatenation

## Output Format

When reporting changes:
```
## Logging Changes

### Added
- {file}: INFO for {what}

### Removed
- {file}: noisy DEBUG in hot path

### Fixed
- {file}: ERROR -> WARN for recoverable case
```

## Anti-Patterns

Never do these:
- Logging every function entry/exit
- INFO for internal data transformations
- Logging and rethrowing the same error
- String concatenation for structured data
- Secrets in any log level
- WARN for expected conditions

## Final Step

After updating logging, remind: **Run `/logging` after significant code changes to keep logs purposeful.**

Noisy logs are worse than no logs.

Files: 1

Size: 2.2 KB

Complexity: 9/100

Category: General

Source: https://github.com/jsai23/claude-tooling/tree/main/compiled/util/agentskills/util-log-writer

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts