1k-sentry

Centralize error monitoring across desktop, web, extension, and mobile apps with Sentry.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/wanghaisheng/web3-scaffold-app-monorepo --skill 1k-sentry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1k-sentry
Source: https://github.com/wanghaisheng/web3-scaffold-app-monorepo/tree/main/.claude/skills/1k-sentry
Command: npx skills add https://github.com/wanghaisheng/web3-scaffold-app-monorepo --skill 1k-sentry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralize error monitoring across desktop, web, extension, and mobile apps using Sentry.

Core Features & Use Cases

  • Platform-aware error tracking and filtering across all client environments
  • Crash report analysis and actionable insights for production issues
  • Custom context, breadcrumbs, and user data to diagnose root causes

Quick Start

Install the Sentry client, initialize it with your DSN, and start capturing errors across all platforms.

Frequently Asked Questions about 1k-sentry

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

FAQPage Schema
How do I set up Sentry error tracking across multiple platforms?

To set up Sentry error tracking across platforms, install the Sentry client, initialize it with your DSN, and define basic options and breadcrumbs in your platform-specific initialization files to start capturing errors.

What is the best way to centralize crash reports from desktop, web, and mobile apps?

Centralize crash reports by applying shared configuration and error filtering rules across platform-specific Sentry setups, enabling unified error monitoring and crash report analysis across all your client environments.

How do error filtering rules work for cross-platform production issues?

Error filtering rules in Sentry work by applying shared configuration across platform-specific setups, allowing you to filter and triage production crash reports consistently across desktop, web, extension, and mobile apps.

How do I add custom context and breadcrumbs to diagnose root causes in Sentry?

Add custom context, breadcrumbs, and user data directly in your code during Sentry initialization to provide actionable insights and diagnose the root causes of production errors.

Do I need a specific Sentry project configuration to track errors across extensions and mobile apps?

Yes, you need an active Sentry project, your specific DSN, and platform-specific initialization files to configure error monitoring and define basic options across desktop, web, extension, and mobile environments.

Can Sentry handle error tracking for both browser extensions and desktop applications?

Yes, Sentry provides platform-aware error tracking and filtering across all client environments, supporting unified crash report analysis and actionable insights for both browser extensions and desktop applications.