{"slug":"sentry-automation","title":"sentry-automation","summary":"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.","platform":"ChatGPT","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-08-16T13:38:50.957229Z","repo":{"url":"https://github.com/sickn33/agentic-awesome-skills","stars":46883,"forks":6831,"license":"MIT","updatedAt":"2026-09-25T05:43:16Z"},"bodyHtml":"<hr>\n<h2>name: sentry-automation\ndescription: \"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.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"</h2>\n<h1>Sentry Automation via Rube MCP</h1>\n<p>Automate Sentry error tracking and monitoring operations through Composio's Sentry toolkit via Rube MCP.</p>\n<h2>Prerequisites</h2>\n<ul>\n<li>Rube MCP must be connected (RUBE_SEARCH_TOOLS available)</li>\n<li>Active Sentry connection via <code>RUBE_MANAGE_CONNECTIONS</code> with toolkit <code>sentry</code></li>\n<li>Always call <code>RUBE_SEARCH_TOOLS</code> first to get current tool schemas</li>\n</ul>\n<h2>Setup</h2>\n<p><strong>Get Rube MCP</strong>: Add <code>https://rube.app/mcp</code> as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.</p>\n<ol>\n<li>Verify Rube MCP is available by confirming <code>RUBE_SEARCH_TOOLS</code> responds</li>\n<li>Call <code>RUBE_MANAGE_CONNECTIONS</code> with toolkit <code>sentry</code></li>\n<li>If connection is not ACTIVE, follow the returned auth link to complete Sentry OAuth</li>\n<li>Confirm connection status shows ACTIVE before running any workflows</li>\n</ol>\n<h2>Core Workflows</h2>\n<h3>1. Investigate Issues</h3>\n<p><strong>When to use</strong>: User wants to find, inspect, or triage error issues</p>\n<p><strong>Tool sequence</strong>:</p>\n<ol>\n<li><code>SENTRY_LIST_AN_ORGANIZATIONS_ISSUES</code> - List issues across the organization [Required]</li>\n<li><code>SENTRY_GET_ORGANIZATION_ISSUE_DETAILS</code> - Get detailed info on a specific issue [Optional]</li>\n<li><code>SENTRY_LIST_AN_ISSUES_EVENTS</code> - View individual error events for an issue [Optional]</li>\n<li><code>SENTRY_RETRIEVE_AN_ISSUE_EVENT</code> - Get full event details with stack trace [Optional]</li>\n<li><code>SENTRY_RETRIEVE_ISSUE_TAG_DETAILS</code> - Inspect tag distribution for an issue [Optional]</li>\n</ol>\n<p><strong>Key parameters</strong>:</p>\n<ul>\n<li><code>organization_id_or_slug</code>: Organization identifier</li>\n<li><code>issue_id</code>: Numeric issue ID</li>\n<li><code>query</code>: Search query (e.g., <code>is:unresolved</code>, <code>assigned:me</code>, <code>browser:Chrome</code>)</li>\n<li><code>sort</code>: Sort order (<code>date</code>, <code>new</code>, <code>freq</code>, <code>priority</code>)</li>\n<li><code>statsPeriod</code>: Time window for stats (<code>24h</code>, <code>14d</code>, etc.)</li>\n</ul>\n<p><strong>Pitfalls</strong>:</p>\n<ul>\n<li><code>organization_id_or_slug</code> is the org slug (e.g., 'my-org'), not the display name</li>\n<li>Issue IDs are numeric; do not confuse with event IDs which are UUIDs</li>\n<li>Query syntax uses Sentry's search format: <code>is:unresolved</code>, <code>assigned:me</code>, <code>!has:release</code></li>\n<li>Events within an issue can have different stack traces; inspect individual events for details</li>\n</ul>\n<h3>2. Manage Project Issues</h3>\n<p><strong>When to use</strong>: User wants to view issues scoped to a specific project</p>\n<p><strong>Tool sequence</strong>:</p>\n<ol>\n<li><code>SENTRY_RETRIEVE_ORGANIZATION_PROJECTS</code> - List projects to find project slug [Prerequisite]</li>\n<li><code>SENTRY_RETRIEVE_PROJECT_ISSUES_LIST</code> - List issues for a specific project [Required]</li>\n<li><code>SENTRY_RETRIEVE_ISSUE_EVENTS_BY_ID</code> - Get events for a specific issue [Optional]</li>\n</ol>\n<p><strong>Key parameters</strong>:</p>\n<ul>\n<li><code>organization_id_or_slug</code>: Organization identifier</li>\n<li><code>project_id_or_slug</code>: Project identifier</li>\n<li><code>query</code>: Search filter string</li>\n<li><code>statsPeriod</code>: Stats time window</li>\n</ul>\n<p><strong>Pitfalls</strong>:</p>\n<ul>\n<li>Project slugs are different from project display names</li>\n<li>Always resolve project names to slugs via RETRIEVE_ORGANIZATION_PROJECTS first</li>\n<li>Project-scoped issue lists may have different pagination than org-scoped lists</li>\n</ul>\n<h3>3. Configure Alert Rules</h3>\n<p><strong>When to use</strong>: User wants to create or manage alert rules for a project</p>\n<p><strong>Tool sequence</strong>:</p>\n<ol>\n<li><code>SENTRY_RETRIEVE_ORGANIZATION_PROJECTS</code> - Find project for the alert [Prerequisite]</li>\n<li><code>SENTRY_RETRIEVE_PROJECT_RULES_BY_ORG_AND_PROJECT_ID</code> - List existing rules [Optional]</li>\n<li><code>SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS</code> - Create a new alert rule [Required]</li>\n<li><code>SENTRY_CREATE_ORGANIZATION_ALERT_RULE</code> - Create org-level metric alert [Alternative]</li>\n<li><code>SENTRY_UPDATE_ORGANIZATION_ALERT_RULES</code> - Update existing alert rules [Optional]</li>\n<li><code>SENTRY_RETRIEVE_ALERT_RULE_DETAILS</code> - Inspect specific alert rule [Optional]</li>\n<li><code>SENTRY_GET_PROJECT_RULE_DETAILS</code> - Get project-level rule details [Optional]</li>\n</ol>\n<p><strong>Key parameters</strong>:</p>\n<ul>\n<li><code>name</code>: Alert rule name</li>\n<li><code>conditions</code>: Array of trigger conditions</li>\n<li><code>actions</code>: Array of actions to perform when triggered</li>\n<li><code>filters</code>: Array of event filters</li>\n<li><code>frequency</code>: How often to trigger (in minutes)</li>\n<li><code>actionMatch</code>: 'all', 'any', or 'none' for condition matching</li>\n</ul>\n<p><strong>Pitfalls</strong>:</p>\n<ul>\n<li>Project-level rules (CREATE_PROJECT_RULE) and org-level metric alerts (CREATE_ORGANIZATION_ALERT_RULE) are different</li>\n<li>Conditions, actions, and filters use specific JSON schemas; check Sentry docs for valid types</li>\n<li><code>frequency</code> is in minutes; setting too low causes alert fatigue</li>\n<li><code>actionMatch</code> defaults may vary; explicitly set to avoid unexpected behavior</li>\n</ul>\n<h3>4. Manage Releases</h3>\n<p><strong>When to use</strong>: User wants to create, track, or manage release versions</p>\n<p><strong>Tool sequence</strong>:</p>\n<ol>\n<li><code>SENTRY_LIST_ORGANIZATION_RELEASES</code> - List existing releases [Optional]</li>\n<li><code>SENTRY_CREATE_RELEASE_FOR_ORGANIZATION</code> - Create a new release [Required]</li>\n<li><code>SENTRY_UPDATE_RELEASE_DETAILS_FOR_ORGANIZATION</code> - Update release metadata [Optional]</li>\n<li><code>SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG</code> - Record a deployment for a release [Optional]</li>\n<li><code>SENTRY_UPLOAD_RELEASE_FILE_TO_ORGANIZATION</code> - Upload source maps or files [Optional]</li>\n</ol>\n<p><strong>Key parameters</strong>:</p>\n<ul>\n<li><code>version</code>: Release version string (e.g., '1.0.0', commit SHA)</li>\n<li><code>projects</code>: Array of project slugs this release belongs to</li>\n<li><code>dateReleased</code>: Release timestamp (ISO 8601)</li>\n<li><code>environment</code>: Deployment environment name (e.g., 'production', 'staging')</li>\n</ul>\n<p><strong>Pitfalls</strong>:</p>\n<ul>\n<li>Release versions must be unique within an organization</li>\n<li>Releases can span multiple projects; use the <code>projects</code> array</li>\n<li>Deploying a release is separate from creating it; use CREATE_RELEASE_DEPLOY</li>\n<li>Source map uploads require the release to exist first</li>\n</ul>\n<h3>5. Monitor Organization and Teams</h3>\n<p><strong>When to use</strong>: User wants to view org structure, teams, or member lists</p>\n<p><strong>Tool sequence</strong>:</p>\n<ol>\n<li><code>SENTRY_GET_ORGANIZATION_DETAILS</code> or <code>SENTRY_GET_ORGANIZATION_BY_ID_OR_SLUG</code> - Get org info [Required]</li>\n<li><code>SENTRY_LIST_TEAMS_IN_ORGANIZATION</code> - List all teams [Optional]</li>\n<li><code>SENTRY_LIST_ORGANIZATION_MEMBERS</code> - List org members [Optional]</li>\n<li><code>SENTRY_GET_PROJECT_LIST</code> - List all accessible projects [Optional]</li>\n</ol>\n<p><strong>Key parameters</strong>:</p>\n<ul>\n<li><code>organization_id_or_slug</code>: Organization identifier</li>\n<li><code>cursor</code>: Pagination cursor for large result sets</li>\n</ul>\n<p><strong>Pitfalls</strong>:</p>\n<ul>\n<li>Organization slugs are URL-safe identifiers, not display names</li>\n<li>Member lists may be paginated; follow cursor pagination</li>\n<li>Team and member visibility depends on the authenticated user's permissions</li>\n</ul>\n<h3>6. Manage Monitors (Cron Monitoring)</h3>\n<p><strong>When to use</strong>: User wants to update cron job monitoring configuration</p>\n<p><strong>Tool sequence</strong>:</p>\n<ol>\n<li><code>SENTRY_UPDATE_A_MONITOR</code> - Update monitor configuration [Required]</li>\n</ol>\n<p><strong>Key parameters</strong>:</p>\n<ul>\n<li><code>organization_id_or_slug</code>: Organization identifier</li>\n<li><code>monitor_id_or_slug</code>: Monitor identifier</li>\n<li><code>name</code>: Monitor display name</li>\n<li><code>schedule</code>: Cron schedule expression or interval</li>\n<li><code>checkin_margin</code>: Grace period in minutes for late check-ins</li>\n<li><code>max_runtime</code>: Maximum expected runtime in minutes</li>\n</ul>\n<p><strong>Pitfalls</strong>:</p>\n<ul>\n<li>Monitor slugs are auto-generated from the name; use slug for API calls</li>\n<li>Schedule changes take effect immediately</li>\n<li>Missing check-ins trigger alerts after the margin period</li>\n</ul>\n<h2>Common Patterns</h2>\n<h3>ID Resolution</h3>\n<p><strong>Organization name -&gt; Slug</strong>:</p>\n<pre><code>1. Call SENTRY_GET_ORGANIZATION_DETAILS\n2. Extract slug field from response\n</code></pre>\n<p><strong>Project name -&gt; Slug</strong>:</p>\n<pre><code>1. Call SENTRY_RETRIEVE_ORGANIZATION_PROJECTS\n2. Find project by name, extract slug\n</code></pre>\n<h3>Pagination</h3>\n<ul>\n<li>Sentry uses cursor-based pagination with <code>Link</code> headers</li>\n<li>Check response for cursor values</li>\n<li>Pass cursor in next request until no more pages</li>\n</ul>\n<h3>Search Query Syntax</h3>\n<ul>\n<li><code>is:unresolved</code> - Unresolved issues</li>\n<li><code>is:resolved</code> - Resolved issues</li>\n<li><code>assigned:me</code> - Assigned to current user</li>\n<li><code>assigned:team-slug</code> - Assigned to a team</li>\n<li><code>!has:release</code> - Issues without a release</li>\n<li><code>first-release:1.0.0</code> - Issues first seen in release</li>\n<li><code>times-seen:&gt;100</code> - Seen more than 100 times</li>\n<li><code>browser:Chrome</code> - Filter by browser tag</li>\n</ul>\n<h2>Known Pitfalls</h2>\n<p><strong>ID Formats</strong>:</p>\n<ul>\n<li>Organization: use slug (e.g., 'my-org'), not display name</li>\n<li>Project: use slug (e.g., 'my-project'), not display name</li>\n<li>Issue IDs: numeric integers</li>\n<li>Event IDs: UUIDs (32-char hex strings)</li>\n</ul>\n<p><strong>Permissions</strong>:</p>\n<ul>\n<li>API token scopes must match the operations being performed</li>\n<li>Organization-level operations require org-level permissions</li>\n<li>Project-level operations require project access</li>\n</ul>\n<p><strong>Rate Limits</strong>:</p>\n<ul>\n<li>Sentry enforces per-organization rate limits</li>\n<li>Implement backoff on 429 responses</li>\n<li>Bulk operations should be staggered</li>\n</ul>\n<h2>Quick Reference</h2>\n<table>\n<thead>\n<tr>\n<th>Task</th>\n<th>Tool Slug</th>\n<th>Key Params</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>List org issues</td>\n<td>SENTRY_LIST_AN_ORGANIZATIONS_ISSUES</td>\n<td>organization_id_or_slug, query</td>\n</tr>\n<tr>\n<td>Get issue details</td>\n<td>SENTRY_GET_ORGANIZATION_ISSUE_DETAILS</td>\n<td>organization_id_or_slug, issue_id</td>\n</tr>\n<tr>\n<td>List issue events</td>\n<td>SENTRY_LIST_AN_ISSUES_EVENTS</td>\n<td>issue_id</td>\n</tr>\n<tr>\n<td>Get event details</td>\n<td>SENTRY_RETRIEVE_AN_ISSUE_EVENT</td>\n<td>organization_id_or_slug, event_id</td>\n</tr>\n<tr>\n<td>List project issues</td>\n<td>SENTRY_RETRIEVE_PROJECT_ISSUES_LIST</td>\n<td>organization_id_or_slug, project_id_or_slug</td>\n</tr>\n<tr>\n<td>List projects</td>\n<td>SENTRY_RETRIEVE_ORGANIZATION_PROJECTS</td>\n<td>organization_id_or_slug</td>\n</tr>\n<tr>\n<td>Get org details</td>\n<td>SENTRY_GET_ORGANIZATION_DETAILS</td>\n<td>organization_id_or_slug</td>\n</tr>\n<tr>\n<td>List teams</td>\n<td>SENTRY_LIST_TEAMS_IN_ORGANIZATION</td>\n<td>organization_id_or_slug</td>\n</tr>\n<tr>\n<td>List members</td>\n<td>SENTRY_LIST_ORGANIZATION_MEMBERS</td>\n<td>organization_id_or_slug</td>\n</tr>\n<tr>\n<td>Create alert rule</td>\n<td>SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS</td>\n<td>organization_id_or_slug, project_id_or_slug</td>\n</tr>\n<tr>\n<td>Create metric alert</td>\n<td>SENTRY_CREATE_ORGANIZATION_ALERT_RULE</td>\n<td>organization_id_or_slug</td>\n</tr>\n<tr>\n<td>Create release</td>\n<td>SENTRY_CREATE_RELEASE_FOR_ORGANIZATION</td>\n<td>organization_id_or_slug, version</td>\n</tr>\n<tr>\n<td>Deploy release</td>\n<td>SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG</td>\n<td>organization_id_or_slug, version</td>\n</tr>\n<tr>\n<td>List releases</td>\n<td>SENTRY_LIST_ORGANIZATION_RELEASES</td>\n<td>organization_id_or_slug</td>\n</tr>\n<tr>\n<td>Update monitor</td>\n<td>SENTRY_UPDATE_A_MONITOR</td>\n<td>organization_id_or_slug, monitor_id_or_slug</td>\n</tr>\n</tbody>\n</table>\n<h2>When to Use</h2>\n<p>This skill is applicable to execute the workflow or actions described in the overview.</p>\n<h2>Limitations</h2>\n<ul>\n<li>Use this skill only when the task clearly matches the scope described above.</li>\n<li>Do not treat the output as a substitute for environment-specific validation, testing, or expert review.</li>\n<li>Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.</li>\n</ul>\n","files":[{"path":"SKILL.md","sizeBytes":10327,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-08-16T13:45:00.612767Z","sha256":"671108076D3728AD0E8840A904C92EF3587FB1F372803CC5E862992C5DC30D2B","sizeBytes":3731},"review":null,"source":{"repositoryUrl":"https://github.com/sickn33/agentic-awesome-skills","path":"skills/sentry-automation","license":"MIT","commit":"f2bba339de74414b0771234cbe4f6a15258e32a3","subtreeSha":"75BFF21084E2A864A057DF6970A06D7238337ED35BE947B5DB3998C4FBF7EC72","lastSyncedAt":"2026-09-25T06:48:39.853703Z"},"reviewedAt":"2026-08-16T13:55:07.848036Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/sentry-automation"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install sickn33-agentic-awesome-skills@llmmart"},{"target":"git","command":"git clone https://github.com/sickn33/agentic-awesome-skills.git"}]}