1.1K skills · sorted by relevance
Inspect production errors recorded in Sentry through read-only API access. Summarize unresolved issues, recent crashes, occurrence counts, and event details to understand what happened and when each problem was last seen.
Investigate WorldMonitor production errors using Sentry event details and source code. Classify issues as noise, already fixed, product bugs, ingestion problems, or needing human review, with tested fixes when code changes are requested.
Review new and spiking Sentry errors, rank their impact, and check for existing GitHub issues. Create triage issues for the highest-impact untracked errors and post a Slack summary, while leaving Sentry error states and assignments unchanged.
Inspect production errors recorded in Sentry using read-only queries. The skill summarizes recent issues, retrieves details of individual error occurrences, and accesses AI-generated cause analysis or fix plans through the command-line tool.
Investigate production errors using Sentry stack traces, which show the code execution path, and events leading up to the failure. Identify likely causes, triggering conditions, affected users, and releases before changing code.
Add Sentry error reporting and performance monitoring to services, scheduled jobs, and database operations. Follow examples for capturing exceptions with useful context and measuring execution time through spans, which record individual operations for investigation.
Investigate and fix production errors reported in Sentry through MCP, a connection to external tools. Analyze error details and execution history, check them against source code, implement fixes, and verify them with tests and regression checks.
Sentry の Issue 一覧 URL（例 `https://<org>.sentry.io/issues/?project=<id>&environment=<env>`）を受け取り、未解決（unresolved）の Issue を列挙して1件ずつサブエージェントで並列調査する。コード上で既に解消済みと確認できたものは Sentry 側を resolved にし、未解消のものは `create-issue` スキルで GitHub Issue を作成する。「Sentryのissueをトリアージして」「Sentryの未解決エラーをチケット化して」といった依頼で使用する。
The English summary is being prepared. Showing the original description.
Investigate Sentry errors by fetching event details and the actions leading up to failures through Composio CLI. Connect error locations to local code, inspect suspect commits, propose patches, run tests, and rank unresolved issues.
Verify production fixes by connecting code changes and releases to Sentry issues. Compare error events and affected users before and after release, then report whether the fix worked, improved behavior, failed, or lacks enough traffic to judge.
Investigate Sentry issues by comparing recent events, error locations in code, tags, environments, releases, and recurrence patterns. Separate observed failures from suspected causes before proposing a fix grounded in the available evidence.
Build an MCP integration skill using a template that reads server-specific reference notes before calling tools. The Sentry example gathers unresolved errors, groups them by likely root cause, and produces a report with investigation suggestions.
Investigate Sentry alerts using Datadog logs and recent GitHub changes, then post an initial diagnosis with a severity assessment. Notify the on-call team when severity reaches the configured threshold or the investigation remains inconclusive, without changing monitored systems.
Investigate service errors in Sentry by project, environment, and time period. Rank problems by event counts and affected users, compare releases or earlier periods, and report findings with links and a clear search scope.
Investigate opaque errors in shipped OpenWork builds using local logs and Sentry exception reports. Identify the change that caused the failure, reproduce it on the affected runtime, file a Linear issue, and reply to the original report.
Help embed Zoom Virtual Agent chat in a website using its web SDK, a developer toolkit. Cover campaign or entry ID launch, event-based controls, user context updates, readiness checks, and browser content security policy requirements.
Set up Sentry error tracking, investigate production failures, and prioritize issues by user impact. Configure useful alerts and analyze performance traces, which show how time is spent across application operations and services.
Integrates Sentry error tracking and performance monitoring into Flutter apps using `sentry_flutter`. Use when setting up crash reporting in Flutter, calling `SentryFlutter.init`, adding `SentryNavigatorObserver` to GoRouter, tracing HTTP requests with `sentry_dio`, capturing handled exceptions via `Sentry.captureException`, adding breadcrumbs, configuring session replay (`replay.onErrorSampleRate`), tuning `tracesSampleRate` or `profilesSampleRate`, controlling PII with `sendDefaultPii`, or setting user context after login and logout.
The English summary is being prepared. Showing the original description.
Set up recurring agent work for issues, tickets, or small fixes. The skill tests one real item first, then defines a repeatable procedure, tracks work to prevent duplicates, and holds outputs for human review.
Assesses a release using Sentry errors, recurring problems, affected users, and crash evidence. Compares equivalent periods with the previous stable release, identifies gaps in the evidence, and recommends rollout actions only when the findings support them.
Compare Sentry issues across selected time windows and releases to find new or recurring problems and changes in frequency or affected users. Prioritize findings using user impact and the strength of available evidence.
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.
The English summary is being prepared. Showing the original description.
Query and manage Sentry error-tracking data — list and search issues, drill into events and stack traces, inspect projects and releases, resolve/ignore issues, and pull stats. Use this whenever the user mentions a Sentry issue, crash, error group, or exception; pastes a sentry.io or self-hosted Sentry URL; asks "why is this erroring", "how many times has this happened", "what's the top error in {project}", "resolve this issue", or wants a Sentry-based digest — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
The English summary is being prepared. Showing the original description.
Prepare user-facing changelog entries for source code changes. The skill determines whether an entry is needed, classifies the change, writes a clear title, and uses the project CLI to create a JSON file tied to the pull request.