226 skills ・ Works with: Sentry · sorted by popularity
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.
Create and maintain Claude Code skills with clear file structure and activation rules. Get guidance on hooks, which run at specific workflow events, plus troubleshooting, edit restrictions, and splitting detailed instructions into reference files.
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.
Investigate production incidents and bugs using logs, metrics, and code evidence. The skill guides hypothesis testing, root cause analysis, fix validation, and reusable investigation notes, with access to configured observability tools such as Axiom.
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.
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.
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.
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.
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.
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.
Analyze gh-aw execution traces, which record individual processing steps, to investigate slow or failing workflows. Using local JSONL files or telemetry backends, the skill checks timing, errors, missing attributes, and trace connections to support focused improvements.
Support authorized external security reconnaissance, the discovery of exposed systems and information. The skill provides search queries, probe references, secret detection patterns, and scoring guidance to help identify assets and organize findings with evidence and confidence levels.
Review access control, authentication flows, and configuration weaknesses across a service. The skill covers invitations, lingering sessions, token permissions, SAML sign-in, and internal APIs, with guidance for comparing response bodies and establishing concrete, reproducible impact.
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
The English summary is being prepared. Showing the original description.
Cross-platform issue triage. Pulls from Sentry (MCP), Linear (MCP), GitHub Issues (gh). Cross-references against code to find already-fixed issues. Auto-resolves fixed ones. Dispatches agents for active issues.
The English summary is being prepared. Showing the original description.
Production incidents dashboard. Reads ECS health, Sentry errors, CI failures. Offers to dispatch fix agents for active fires.
The English summary is being prepared. Showing the original description.
Autonomous multi-project orchestration engine. Audits all registered projects, structures work into dependency-wired tasks, dispatches parallel agents (subagents or Agent Teams), audits completions, and ships PRs. Registry-driven — works for any user with a configured project registry.
The English summary is being prepared. Showing the original description.
Interactive pixel-art command center dashboard. Visual business HQ with instant hotkey navigation to all ops commands, live status indicators, fire alerts, C-suite reports, settings, sharing, and FAQ.
The English summary is being prepared. Showing the original description.
Interactive setup wizard for the claude-ops plugin. Installs missing CLIs, configures env vars for each channel (Telegram, WhatsApp, Email, Slack, Notion, Linear, Sentry, Vercel), builds the project registry, and saves user preferences. Run once after installing the plugin or any time to reconfigure.
The English summary is being prepared. Showing the original description.
Automate Sentry tasks via Rube MCP (Composio): manage issues/events, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas.
The English summary is being prepared. Showing the original description.
Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports github.com/samber/oops.
The English summary is being prepared. Showing the original description.
Structured logging extensions for Golang using samber/slog-**** packages — multi-handler pipelines (slog-multi), log sampling (slog-sampling), attribute formatting (slog-formatter), HTTP middleware (slog-fiber, slog-gin, slog-chi, slog-echo), and backend routing (slog-datadog, slog-sentry, slog-loki, slog-syslog, slog-logstash, slog-graylog...). Apply when using or adopting slog, or when the codebase already imports any github.com/samber/slog-* package.
The English summary is being prepared. Showing the original description.
Comprehensive Content Security Policy audit for MCP Apps in sandboxed iframes. Discovers all network origins, traces them to source, and generates CSP configuration for registerAppResource.
The English summary is being prepared. Showing the original description.
Diagnose software failures using observability data, ranked hypotheses, and targeted instrumentation. Use when the cause is unclear or an issue requires systematic investigation.
The English summary is being prepared. Showing the original description.