Agent skill · marketing growth · aiskillstore
sentry-automation
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.
Why this skill is useful
Adds specific commands and workflows for automating Sentry tasks that the AI wouldn't reliably generate on its own.
What it needs
Requires sentry account access. About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Sentry Automation via Rube MCP Automate Sentry error tracking and monitoring operations through Composio's Sentry toolkit via Rube MCP. Prerequisites Rube MCP must be connected (RUBESEARCHTOOLS available) Active Sentry connection via RUBEMANAGECONNECTIONS with toolkit sentry Always call RUBESEARCHTOOLS first to get current tool schemas Setup Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. 1. Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds 2. Call RUBEMANAGECONNECTIONS with toolkit sentry 3. If connection is not ACTIVE, follow the returned auth link to complete Sentry OAuth 4. Confirm connection status shows ACTIVE before running any workflows Core Workflows 1. Investigate Issues When to use: User wants to find, inspect, or triage error issues Tool sequence: 1. SENTRYLISTANORGANIZATIONSISSUES - List issues across the organization [Required] 2. SENTRYGETORGANIZATIONISSUEDETAILS - Get detailed info on a specific issue [Optional] 3. SENTRYLISTANISSUESEVENTS - View individual error events for an issue [Optional] 4. SENTRYRETRIEVEANISSUEEVENT - Get full event details with stack trace [Optional] 5. SENTRYRETRIEVEISSUETAGDETAILS - Inspect tag distribution for an issue [Optional] Key parameters: organizationidorslug: Organization identifier issueid: Numeric issue ID query: Search query (e.g., is:unresolved, assigned:me, browser:Chrome) sort: Sort order (date, new, freq, priority) statsPeriod: Time window for stats (24h, 14d, etc.) Pitfalls: organizationidorslug is the org slug (e.g., 'my-org'), not the display name Issue IDs are numeric; do not confuse with event IDs which are UUIDs Query syntax uses Sentry's search format: is:unresolved, assigned:me, !has:release Events within an issue can have different stack traces; inspect individual events for details 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/sentry-automation