api-observability-axiom-pino-sentry
Pino logging, Sentry error tracking, Axiom - structured logging with correlation IDs, error boundaries, performance monitoring, alerting
npx skills add majiayu000/claude-skill-registry --skill api-observability-axiom-pino-sentry --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Observability Patterns (Logging, Tracing, Error Handling) > **Quick Guide:** Structured logging with Pino (debug/info/warn/error). Correlation IDs for request tracing. Sentry error boundaries in React. Attach user context after auth. Filter expected errors (404s). Create Axiom monitors for alerts. --- <critical_requirements> ## CRITICAL: Before Using This Skill > **All code must follow project conventions in CLAUDE.md** (kebab-case, named exports, import ordering, `import type`, named constants) **(You MUST include correlation ID in ALL log statements for request tracing)** **(You MUST use structured logging with required fields: level, message, correlationId, timestamp)** **(You MUST filter expected errors (404, validation) from Sentry to avoid quota waste)** **(You MUST attach user context to Sentry AFTER authentication completes)** **(You MUST use child loggers with context instead of repeating fields in every log call)** </critical_requirements> --- **Auto-detection:** log, logger, pino, Sentry, error boundary, correlation ID, trace, span, observability, monitoring, alerting **When to use:** - Adding logging to new feature code - Implementing error handling patterns - Setting
- CRITICAL: Before Using This Skill
- Philosophy
- Core Patterns
- Pattern 1: Log Levels Decision Tree
- Pattern 2: Structured Logging with Required Fields
- Pattern 3: Correlation IDs for Request Tracing
- Pattern 4: Custom Traces and Spans with OpenTelemetry
- Pattern 5: Sentry Error Boundaries in React (App Router)
- Pattern 6: Attaching User Context to Sentry
- Pattern 7: Filtering Expected Errors
- Pattern 8: Creating Axiom Monitors and Alerts
- Pattern 9: Performance Monitoring Patterns
- Pattern 10: Debugging Guide - Tracing a Request
- Integration Guide
What does the api-observability-axiom-pino-sentry skill do?
Pino logging, Sentry error tracking, Axiom - structured logging with correlation IDs, error boundaries, performance monitoring, alerting
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill api-observability-axiom-pino-sentry --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.