Sentry

Sentry captures errors and crashes and ties each one to the release, request and exact line that caused it; beyond errors it records traces, logs, metrics, profiles, Session Replay, crons, uptime and AI monitoring, all joined by one trace ID. Per-platform setup comes from the current Sentry docs, not memory: every docs page is served as Markdown by appending .md to its URL (catalog: https://docs.sentry.io/platforms.md). Most outcomes come down to three things: the platform's init runs before the code that fails, the event is confirmed in Sentry rather than assumed, and production stack traces are readable. Vendor-neutral OpenTelemetry is the observability skill.

Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]