Sentry

Capture and trace application errors with Sentry SDK and DSN configuration.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/monam2/traders --skill sentry-monam2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Sentry
Source: https://github.com/monam2/traders/tree/main/.agent/skills/sentry
Command: npx skills add https://github.com/monam2/traders --skill sentry-monam2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detecting and resolving runtime errors across the full stack can be time-consuming and disruptive. This skill provides centralized error monitoring and tracing to shorten incident response times and improve product reliability.

Core Features & Use Cases

  • Automatic frontend and API error capture with rich context (user data, environment, and stack traces).
  • Manual error capture and custom tagging to surface critical issues quickly.
  • Performance tracing, error reporting, and incident analysis support.

Quick Start

Initialize the Sentry SDK and configure the DSN to start capturing errors immediately.

Frequently Asked Questions about Sentry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does error monitoring trace runtime issues across frontend and API routes?

Error monitoring captures automatic errors and manual captures across frontend and API routes, attaching user context and stack traces to reduce incident response time.

What is the best way to monitor application errors in modern stacks?

The best way to monitor application errors is by initializing the Sentry SDK and configuring the DSN to automatically capture frontend and backend errors with rich context.

Do I need environment variables to configure error monitoring and tracing?

Yes, you need to configure the DSN via environment variables to initialize the SDK and start capturing runtime errors and performance traces.

Can I use custom tagging to surface critical application errors?

Yes, custom tagging allows you to manually capture errors and add specific contextual data, helping you quickly surface and analyze critical issues.

Does this error monitoring work with background jobs in modern stacks?

Yes, error monitoring works across frontend, API routes, and background jobs in modern stacks to capture automatic errors and contextual data.

Why do I need performance tracing for bug-tracking and incident analysis?

Performance tracing is needed to monitor application errors end-to-end, providing the contextual data required for incident analysis and reducing mean time to repair.