메뉴
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.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/aAAaqwq/AGI-Super-Team --skill sentry-automation명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | sentry-automation |
| 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. |
| requires | {"mcp":["rube"]} |
Automate Sentry error tracking and monitoring operations through Composio's Sentry toolkit via Rube MCP.
RUBE_MANAGE_CONNECTIONS with toolkit sentryRUBE_SEARCH_TOOLS first to get current tool schemasGet 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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit sentryWhen to use: User wants to find, inspect, or triage error issues
Tool sequence:
SENTRY_LIST_AN_ORGANIZATIONS_ISSUES - List issues across the organization [Required]SENTRY_GET_ORGANIZATION_ISSUE_DETAILS - Get detailed info on a specific issue [Optional]SENTRY_LIST_AN_ISSUES_EVENTS - View individual error events for an issue [Optional]SENTRY_RETRIEVE_AN_ISSUE_EVENT - Get full event details with stack trace [Optional]SENTRY_RETRIEVE_ISSUE_TAG_DETAILS - Inspect tag distribution for an issue [Optional]Key parameters:
organization_id_or_slug: Organization identifierissue_id: Numeric issue IDquery: 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:
organization_id_or_slug is the org slug (e.g., 'my-org'), not the display nameis:unresolved, assigned:me, !has:releaseWhen to use: User wants to view issues scoped to a specific project
Tool sequence:
SENTRY_RETRIEVE_ORGANIZATION_PROJECTS - List projects to find project slug [Prerequisite]SENTRY_RETRIEVE_PROJECT_ISSUES_LIST - List issues for a specific project [Required]SENTRY_RETRIEVE_ISSUE_EVENTS_BY_ID - Get events for a specific issue [Optional]Key parameters:
organization_id_or_slug: Organization identifierproject_id_or_slug: Project identifierquery: Search filter stringstatsPeriod: Stats time windowPitfalls:
When to use: User wants to create or manage alert rules for a project
Tool sequence:
SENTRY_RETRIEVE_ORGANIZATION_PROJECTS - Find project for the alert [Prerequisite]SENTRY_RETRIEVE_PROJECT_RULES_BY_ORG_AND_PROJECT_ID - List existing rules [Optional]SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS - Create a new alert rule [Required]SENTRY_CREATE_ORGANIZATION_ALERT_RULE - Create org-level metric alert [Alternative]SENTRY_UPDATE_ORGANIZATION_ALERT_RULES - Update existing alert rules [Optional]SENTRY_RETRIEVE_ALERT_RULE_DETAILS - Inspect specific alert rule [Optional]SENTRY_GET_PROJECT_RULE_DETAILS - Get project-level rule details [Optional]Key parameters:
name: Alert rule nameconditions: Array of trigger conditionsactions: Array of actions to perform when triggeredfilters: Array of event filtersfrequency: How often to trigger (in minutes)actionMatch: 'all', 'any', or 'none' for condition matchingPitfalls:
frequency is in minutes; setting too low causes alert fatigueactionMatch defaults may vary; explicitly set to avoid unexpected behaviorWhen to use: User wants to create, track, or manage release versions
Tool sequence:
SENTRY_LIST_ORGANIZATION_RELEASES - List existing releases [Optional]SENTRY_CREATE_RELEASE_FOR_ORGANIZATION - Create a new release [Required]SENTRY_UPDATE_RELEASE_DETAILS_FOR_ORGANIZATION - Update release metadata [Optional]SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG - Record a deployment for a release [Optional]SENTRY_UPLOAD_RELEASE_FILE_TO_ORGANIZATION - Upload source maps or files [Optional]Key parameters:
version: Release version string (e.g., '1.0.0', commit SHA)projects: Array of project slugs this release belongs todateReleased: Release timestamp (ISO 8601)environment: Deployment environment name (e.g., 'production', 'staging')Pitfalls:
projects arrayWhen to use: User wants to view org structure, teams, or member lists
Tool sequence:
SENTRY_GET_ORGANIZATION_DETAILS or SENTRY_GET_ORGANIZATION_BY_ID_OR_SLUG - Get org info [Required]SENTRY_LIST_TEAMS_IN_ORGANIZATION - List all teams [Optional]SENTRY_LIST_ORGANIZATION_MEMBERS - List org members [Optional]SENTRY_GET_PROJECT_LIST - List all accessible projects [Optional]Key parameters:
organization_id_or_slug: Organization identifiercursor: Pagination cursor for large result setsPitfalls:
When to use: User wants to update cron job monitoring configuration
Tool sequence:
SENTRY_UPDATE_A_MONITOR - Update monitor configuration [Required]Key parameters:
organization_id_or_slug: Organization identifiermonitor_id_or_slug: Monitor identifiername: Monitor display nameschedule: Cron schedule expression or intervalcheckin_margin: Grace period in minutes for late check-insmax_runtime: Maximum expected runtime in minutesPitfalls:
Organization name -> Slug:
1. Call SENTRY_GET_ORGANIZATION_DETAILS
2. Extract slug field from response
Project name -> Slug:
1. Call SENTRY_RETRIEVE_ORGANIZATION_PROJECTS
2. Find project by name, extract slug
Link headersis:unresolved - Unresolved issuesis:resolved - Resolved issuesassigned:me - Assigned to current userassigned:team-slug - Assigned to a team!has:release - Issues without a releasefirst-release:1.0.0 - Issues first seen in releasetimes-seen:>100 - Seen more than 100 timesbrowser:Chrome - Filter by browser tagID Formats:
Permissions:
Rate Limits:
| Task | Tool Slug | Key Params |
|---|---|---|
| List org issues | SENTRY_LIST_AN_ORGANIZATIONS_ISSUES | organization_id_or_slug, query |
| Get issue details | SENTRY_GET_ORGANIZATION_ISSUE_DETAILS | organization_id_or_slug, issue_id |
| List issue events | SENTRY_LIST_AN_ISSUES_EVENTS | issue_id |
| Get event details | SENTRY_RETRIEVE_AN_ISSUE_EVENT | organization_id_or_slug, event_id |
| List project issues | SENTRY_RETRIEVE_PROJECT_ISSUES_LIST | organization_id_or_slug, project_id_or_slug |
| List projects | SENTRY_RETRIEVE_ORGANIZATION_PROJECTS | organization_id_or_slug |
| Get org details | SENTRY_GET_ORGANIZATION_DETAILS | organization_id_or_slug |
| List teams | SENTRY_LIST_TEAMS_IN_ORGANIZATION | organization_id_or_slug |
| List members | SENTRY_LIST_ORGANIZATION_MEMBERS | organization_id_or_slug |
| Create alert rule | SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS | organization_id_or_slug, project_id_or_slug |
| Create metric alert | SENTRY_CREATE_ORGANIZATION_ALERT_RULE | organization_id_or_slug |
| Create release | SENTRY_CREATE_RELEASE_FOR_ORGANIZATION | organization_id_or_slug, version |
| Deploy release | SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG | organization_id_or_slug, version |
| List releases | SENTRY_LIST_ORGANIZATION_RELEASES | organization_id_or_slug |
| Update monitor | SENTRY_UPDATE_A_MONITOR | organization_id_or_slug, monitor_id_or_slug |