[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EZVG3KTSC3CMHQR5CMF17R":3,"skill-same:01M6EZVG3KTSC3CMHQR5CMF17R":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6EZVG3KTSC3CMHQR5CMF17R","sentry-automation",null,"Automate Sentry tasks via Rube MCP (Composio): manage issues\u002Fevents, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",67,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fsickn33\u002Fsentry-automation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"automation","sentry automation","sentry","via","MCP","events","alerts","composio","manage","releases","automate","projects","configure","first","Tools","search","issues","teams","tasks","monitor","2026-11-10 10:12:30",false,"---\nname: sentry-automation\ndescription: \"Automate Sentry tasks via Rube MCP (Composio): manage issues\u002Fevents, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\n---\n\n# Sentry Automation via Rube MCP\n\nAutomate Sentry error tracking and monitoring operations through Composio's Sentry toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Sentry connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sentry`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sentry`\n3. If connection is not ACTIVE, follow the returned auth link to complete Sentry OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Investigate Issues\n\n**When to use**: User wants to find, inspect, or triage error issues\n\n**Tool sequence**:\n1. `SENTRY_LIST_AN_ORGANIZATIONS_ISSUES` - List issues across the organization [Required]\n2. `SENTRY_GET_ORGANIZATION_ISSUE_DETAILS` - Get detailed info on a specific issue [Optional]\n3. `SENTRY_LIST_AN_ISSUES_EVENTS` - View individual error events for an issue [Optional]\n4. `SENTRY_RETRIEVE_AN_ISSUE_EVENT` - Get full event details with stack trace [Optional]\n5. `SENTRY_RETRIEVE_ISSUE_TAG_DETAILS` - Inspect tag distribution for an issue [Optional]\n\n**Key parameters**:\n- `organization_id_or_slug`: Organization identifier\n- `issue_id`: Numeric issue ID\n- `query`: Search query (e.g., `is:unresolved`, `assigned:me`, `browser:Chrome`)\n- `sort`: Sort order (`date`, `new`, `freq`, `priority`)\n- `statsPeriod`: Time window for stats (`24h`, `14d`, etc.)\n\n**Pitfalls**:\n- `organization_id_or_slug` is the org slug (e.g., 'my-org'), not the display name\n- Issue IDs are numeric; do not confuse with event IDs which are UUIDs\n- Query syntax uses Sentry's search format: `is:unresolved`, `assigned:me`, `!has:release`\n- Events within an issue can have different stack traces; inspect individual events for details\n\n### 2. Manage Project Issues\n\n**When to use**: User wants to view issues scoped to a specific project\n\n**Tool sequence**:\n1. `SENTRY_RETRIEVE_ORGANIZATION_PROJECTS` - List projects to find project slug [Prerequisite]\n2. `SENTRY_RETRIEVE_PROJECT_ISSUES_LIST` - List issues for a specific project [Required]\n3. `SENTRY_RETRIEVE_ISSUE_EVENTS_BY_ID` - Get events for a specific issue [Optional]\n\n**Key parameters**:\n- `organization_id_or_slug`: Organization identifier\n- `project_id_or_slug`: Project identifier\n- `query`: Search filter string\n- `statsPeriod`: Stats time window\n\n**Pitfalls**:\n- Project slugs are different from project display names\n- Always resolve project names to slugs via RETRIEVE_ORGANIZATION_PROJECTS first\n- Project-scoped issue lists may have different pagination than org-scoped lists\n\n### 3. Configure Alert Rules\n\n**When to use**: User wants to create or manage alert rules for a project\n\n**Tool sequence**:\n1. `SENTRY_RETRIEVE_ORGANIZATION_PROJECTS` - Find project for the alert [Prerequisite]\n2. `SENTRY_RETRIEVE_PROJECT_RULES_BY_ORG_AND_PROJECT_ID` - List existing rules [Optional]\n3. `SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS` - Create a new alert rule [Required]\n4. `SENTRY_CREATE_ORGANIZATION_ALERT_RULE` - Create org-level metric alert [Alternative]\n5. `SENTRY_UPDATE_ORGANIZATION_ALERT_RULES` - Update existing alert rules [Optional]\n6. `SENTRY_RETRIEVE_ALERT_RULE_DETAILS` - Inspect specific alert rule [Optional]\n7. `SENTRY_GET_PROJECT_RULE_DETAILS` - Get project-level rule details [Optional]\n\n**Key parameters**:\n- `name`: Alert rule name\n- `conditions`: Array of trigger conditions\n- `actions`: Array of actions to perform when triggered\n- `filters`: Array of event filters\n- `frequency`: How often to trigger (in minutes)\n- `actionMatch`: 'all', 'any', or 'none' for condition matching\n\n**Pitfalls**:\n- Project-level rules (CREATE_PROJECT_RULE) and org-level metric alerts (CREATE_ORGANIZATION_ALERT_RULE) are different\n- Conditions, actions, and filters use specific JSON schemas; check Sentry docs for valid types\n- `frequency` is in minutes; setting too low causes alert fatigue\n- `actionMatch` defaults may vary; explicitly set to avoid unexpected behavior\n\n### 4. Manage Releases\n\n**When to use**: User wants to create, track, or manage release versions\n\n**Tool sequence**:\n1. `SENTRY_LIST_ORGANIZATION_RELEASES` - List existing releases [Optional]\n2. `SENTRY_CREATE_RELEASE_FOR_ORGANIZATION` - Create a new release [Required]\n3. `SENTRY_UPDATE_RELEASE_DETAILS_FOR_ORGANIZATION` - Update release metadata [Optional]\n4. `SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG` - Record a deployment for a release [Optional]\n5. `SENTRY_UPLOAD_RELEASE_FILE_TO_ORGANIZATION` - Upload source maps or files [Optional]\n\n**Key parameters**:\n- `version`: Release version string (e.g., '1.0.0', commit SHA)\n- `projects`: Array of project slugs this release belongs to\n- `dateReleased`: Release timestamp (ISO 8601)\n- `environment`: Deployment environment name (e.g., 'production', 'staging')\n\n**Pitfalls**:\n- Release versions must be unique within an organization\n- Releases can span multiple projects; use the `projects` array\n- Deploying a release is separate from creating it; use CREATE_RELEASE_DEPLOY\n- Source map uploads require the release to exist first\n\n### 5. Monitor Organization and Teams\n\n**When to use**: User wants to view org structure, teams, or member lists\n\n**Tool sequence**:\n1. `SENTRY_GET_ORGANIZATION_DETAILS` or `SENTRY_GET_ORGANIZATION_BY_ID_OR_SLUG` - Get org info [Required]\n2. `SENTRY_LIST_TEAMS_IN_ORGANIZATION` - List all teams [Optional]\n3. `SENTRY_LIST_ORGANIZATION_MEMBERS` - List org members [Optional]\n4. `SENTRY_GET_PROJECT_LIST` - List all accessible projects [Optional]\n\n**Key parameters**:\n- `organization_id_or_slug`: Organization identifier\n- `cursor`: Pagination cursor for large result sets\n\n**Pitfalls**:\n- Organization slugs are URL-safe identifiers, not display names\n- Member lists may be paginated; follow cursor pagination\n- Team and member visibility depends on the authenticated user's permissions\n\n### 6. Manage Monitors (Cron Monitoring)\n\n**When to use**: User wants to update cron job monitoring configuration\n\n**Tool sequence**:\n1. `SENTRY_UPDATE_A_MONITOR` - Update monitor configuration [Required]\n\n**Key parameters**:\n- `organization_id_or_slug`: Organization identifier\n- `monitor_id_or_slug`: Monitor identifier\n- `name`: Monitor display name\n- `schedule`: Cron schedule expression or interval\n- `checkin_margin`: Grace period in minutes for late check-ins\n- `max_runtime`: Maximum expected runtime in minutes\n\n**Pitfalls**:\n- Monitor slugs are auto-generated from the name; use slug for API calls\n- Schedule changes take effect immediately\n- Missing check-ins trigger alerts after the margin period\n\n## Common Patterns\n\n### ID Resolution\n\n**Organization name -> Slug**:\n```\n1. Call SENTRY_GET_ORGANIZATION_DETAILS\n2. Extract slug field from response\n```\n\n**Project name -> Slug**:\n```\n1. Call SENTRY_RETRIEVE_ORGANIZATION_PROJECTS\n2. Find project by name, extract slug\n```\n\n### Pagination\n\n- Sentry uses cursor-based pagination with `Link` headers\n- Check response for cursor values\n- Pass cursor in next request until no more pages\n\n### Search Query Syntax\n\n- `is:unresolved` - Unresolved issues\n- `is:resolved` - Resolved issues\n- `assigned:me` - Assigned to current user\n- `assigned:team-slug` - Assigned to a team\n- `!has:release` - Issues without a release\n- `first-release:1.0.0` - Issues first seen in release\n- `times-seen:>100` - Seen more than 100 times\n- `browser:Chrome` - Filter by browser tag\n\n## Known Pitfalls\n\n**ID Formats**:\n- Organization: use slug (e.g., 'my-org'), not display name\n- Project: use slug (e.g., 'my-project'), not display name\n- Issue IDs: numeric integers\n- Event IDs: UUIDs (32-char hex strings)\n\n**Permissions**:\n- API token scopes must match the operations being performed\n- Organization-level operations require org-level permissions\n- Project-level operations require project access\n\n**Rate Limits**:\n- Sentry enforces per-organization rate limits\n- Implement backoff on 429 responses\n- Bulk operations should be staggered\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List org issues | SENTRY_LIST_AN_ORGANIZATIONS_ISSUES | organization_id_or_slug, query |\n| Get issue details | SENTRY_GET_ORGANIZATION_ISSUE_DETAILS | organization_id_or_slug, issue_id |\n| List issue events | SENTRY_LIST_AN_ISSUES_EVENTS | issue_id |\n| Get event details | SENTRY_RETRIEVE_AN_ISSUE_EVENT | organization_id_or_slug, event_id |\n| List project issues | SENTRY_RETRIEVE_PROJECT_ISSUES_LIST | organization_id_or_slug, project_id_or_slug |\n| List projects | SENTRY_RETRIEVE_ORGANIZATION_PROJECTS | organization_id_or_slug |\n| Get org details | SENTRY_GET_ORGANIZATION_DETAILS | organization_id_or_slug |\n| List teams | SENTRY_LIST_TEAMS_IN_ORGANIZATION | organization_id_or_slug |\n| List members | SENTRY_LIST_ORGANIZATION_MEMBERS | organization_id_or_slug |\n| Create alert rule | SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS | organization_id_or_slug, project_id_or_slug |\n| Create metric alert | SENTRY_CREATE_ORGANIZATION_ALERT_RULE | organization_id_or_slug |\n| Create release | SENTRY_CREATE_RELEASE_FOR_ORGANIZATION | organization_id_or_slug, version |\n| Deploy release | SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG | organization_id_or_slug, version |\n| List releases | SENTRY_LIST_ORGANIZATION_RELEASES | organization_id_or_slug |\n| Update monitor | SENTRY_UPDATE_A_MONITOR | organization_id_or_slug, monitor_id_or_slug |\n","# Sentry Automation via Rube MCP\n\nAutomate Sentry error tracking and monitoring operations through Composio's Sentry toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Sentry connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sentry`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `sentry`\n3. If connection is not ACTIVE, follow the returned auth link to complete Sentry OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Investigate Issues\n\n**When to use**: User wants to find, inspect, or triage error issues\n\n**Tool sequence**:\n1. `SENTRY_LIST_AN_ORGANIZATIONS_ISSUES` - List issues across the organization [Required]\n2. `SENTRY_GET_ORGANIZATION_ISSUE_DETAILS` - Get detailed info on a specific issue [Optional]\n3. `SENTRY_LIST_AN_ISSUES_EVENTS` - View individual error events for an issue [Optional]\n4. `SENTRY_RETRIEVE_AN_ISSUE_EVENT` - Get full event details with stack trace [Optional]\n5. `SENTRY_RETRIEVE_ISSUE_TAG_DETAILS` - Inspect tag distribution for an issue [Optional]\n\n**Key parameters**:\n- `organization_id_or_slug`: Organization identifier\n- `issue_id`: Numeric issue ID\n- `query`: Search query (e.g., `is:unresolved`, `assigned:me`, `browser:Chrome`)\n- `sort`: Sort order (`date`, `new`, `freq`, `priority`)\n- `statsPeriod`: Time window for stats (`24h`, `14d`, etc.)\n\n**Pitfalls**:\n- `organization_id_or_slug` is the org slug (e.g., 'my-org'), not the display name\n- Issue IDs are numeric; do not confuse with event IDs which are UUIDs\n- Query syntax uses Sentry's search format: `is:unresolved`, `assigned:me`, `!has:release`\n- Events within an issue can have different stack traces; inspect individual events for details\n\n### 2. Manage Project Issues\n\n**When to use**: User wants to view issues scoped to a specific project\n\n**Tool sequence**:\n1. `SENTRY_RETRIEVE_ORGANIZATION_PROJECTS` - List projects to find project slug [Prerequisite]\n2. `SENTRY_RETRIEVE_PROJECT_ISSUES_LIST` - List issues for a specific project [Required]\n3. `SENTRY_RETRIEVE_ISSUE_EVENTS_BY_ID` - Get events for a specific issue [Optional]\n\n**Key parameters**:\n- `organization_id_or_slug`: Organization identifier\n- `project_id_or_slug`: Project identifier\n- `query`: Search filter string\n- `statsPeriod`: Stats time window\n\n**Pitfalls**:\n- Project slugs are different from project display names\n- Always resolve project names to slugs via RETRIEVE_ORGANIZATION_PROJECTS first\n- Project-scoped issue lists may have different pagination than org-scoped lists\n\n### 3. Configure Alert Rules\n\n**When to use**: User wants to create or manage alert rules for a project\n\n**Tool sequence**:\n1. `SENTRY_RETRIEVE_ORGANIZATION_PROJECTS` - Find project for the alert [Prerequisite]\n2. `SENTRY_RETRIEVE_PROJECT_RULES_BY_ORG_AND_PROJECT_ID` - List existing rules [Optional]\n3. `SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS` - Create a new alert rule [Required]\n4. `SENTRY_CREATE_ORGANIZATION_ALERT_RULE` - Create org-level metric alert [Alternative]\n5. `SENTRY_UPDATE_ORGANIZATION_ALERT_RULES` - Update existing alert rules [Optional]\n6. `SENTRY_RETRIEVE_ALERT_RULE_DETAILS` - Inspect specific alert rule [Optional]\n7. `SENTRY_GET_PROJECT_RULE_DETAILS` - Get project-level rule details [Optional]\n\n**Key parameters**:\n- `name`: Alert rule name\n- `conditions`: Array of trigger conditions\n- `actions`: Array of actions to perform when triggered\n- `filters`: Array of event filters\n- `frequency`: How often to trigger (in minutes)\n- `actionMatch`: 'all', 'any', or 'none' for condition matching\n\n**Pitfalls**:\n- Project-level rules (CREATE_PROJECT_RULE) and org-level metric alerts (CREATE_ORGANIZATION_ALERT_RULE) are different\n- Conditions, actions, and filters use specific JSON schemas; check Sentry docs for valid types\n- `frequency` is in minutes; setting too low causes alert fatigue\n- `actionMatch` defaults may vary; explicitly set to avoid unexpected behavior\n\n### 4. Manage Releases\n\n**When to use**: User wants to create, track, or manage release versions\n\n**Tool sequence**:\n1. `SENTRY_LIST_ORGANIZATION_RELEASES` - List existing releases [Optional]\n2. `SENTRY_CREATE_RELEASE_FOR_ORGANIZATION` - Create a new release [Required]\n3. `SENTRY_UPDATE_RELEASE_DETAILS_FOR_ORGANIZATION` - Update release metadata [Optional]\n4. `SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG` - Record a deployment for a release [Optional]\n5. `SENTRY_UPLOAD_RELEASE_FILE_TO_ORGANIZATION` - Upload source maps or files [Optional]\n\n**Key parameters**:\n- `version`: Release version string (e.g., '1.0.0', commit SHA)\n- `projects`: Array of project slugs this release belongs to\n- `dateReleased`: Release timestamp (ISO 8601)\n- `environment`: Deployment environment name (e.g., 'production', 'staging')\n\n**Pitfalls**:\n- Release versions must be unique within an organization\n- Releases can span multiple projects; use the `projects` array\n- Deploying a release is separate from creating it; use CREATE_RELEASE_DEPLOY\n- Source map uploads require the release to exist first\n\n### 5. Monitor Organization and Teams\n\n**When to use**: User wants to view org structure, teams, or member lists\n\n**Tool sequence**:\n1. `SENTRY_GET_ORGANIZATION_DETAILS` or `SENTRY_GET_ORGANIZATION_BY_ID_OR_SLUG` - Get org info [Required]\n2. `SENTRY_LIST_TEAMS_IN_ORGANIZATION` - List all teams [Optional]\n3. `SENTRY_LIST_ORGANIZATION_MEMBERS` - List org members [Optional]\n4. `SENTRY_GET_PROJECT_LIST` - List all accessible projects [Optional]\n\n**Key parameters**:\n- `organization_id_or_slug`: Organization identifier\n- `cursor`: Pagination cursor for large result sets\n\n**Pitfalls**:\n- Organization slugs are URL-safe identifiers, not display names\n- Member lists may be paginated; follow cursor pagination\n- Team and member visibility depends on the authenticated user's permissions\n\n### 6. Manage Monitors (Cron Monitoring)\n\n**When to use**: User wants to update cron job monitoring configuration\n\n**Tool sequence**:\n1. `SENTRY_UPDATE_A_MONITOR` - Update monitor configuration [Required]\n\n**Key parameters**:\n- `organization_id_or_slug`: Organization identifier\n- `monitor_id_or_slug`: Monitor identifier\n- `name`: Monitor display name\n- `schedule`: Cron schedule expression or interval\n- `checkin_margin`: Grace period in minutes for late check-ins\n- `max_runtime`: Maximum expected runtime in minutes\n\n**Pitfalls**:\n- Monitor slugs are auto-generated from the name; use slug for API calls\n- Schedule changes take effect immediately\n- Missing check-ins trigger alerts after the margin period\n\n## Common Patterns\n\n### ID Resolution\n\n**Organization name -> Slug**:\n```\n1. Call SENTRY_GET_ORGANIZATION_DETAILS\n2. Extract slug field from response\n```\n\n**Project name -> Slug**:\n```\n1. Call SENTRY_RETRIEVE_ORGANIZATION_PROJECTS\n2. Find project by name, extract slug\n```\n\n### Pagination\n\n- Sentry uses cursor-based pagination with `Link` headers\n- Check response for cursor values\n- Pass cursor in next request until no more pages\n\n### Search Query Syntax\n\n- `is:unresolved` - Unresolved issues\n- `is:resolved` - Resolved issues\n- `assigned:me` - Assigned to current user\n- `assigned:team-slug` - Assigned to a team\n- `!has:release` - Issues without a release\n- `first-release:1.0.0` - Issues first seen in release\n- `times-seen:>100` - Seen more than 100 times\n- `browser:Chrome` - Filter by browser tag\n\n## Known Pitfalls\n\n**ID Formats**:\n- Organization: use slug (e.g., 'my-org'), not display name\n- Project: use slug (e.g., 'my-project'), not display name\n- Issue IDs: numeric integers\n- Event IDs: UUIDs (32-char hex strings)\n\n**Permissions**:\n- API token scopes must match the operations being performed\n- Organization-level operations require org-level permissions\n- Project-level operations require project access\n\n**Rate Limits**:\n- Sentry enforces per-organization rate limits\n- Implement backoff on 429 responses\n- Bulk operations should be staggered\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List org issues | SENTRY_LIST_AN_ORGANIZATIONS_ISSUES | organization_id_or_slug, query |\n| Get issue details | SENTRY_GET_ORGANIZATION_ISSUE_DETAILS | organization_id_or_slug, issue_id |\n| List issue events | SENTRY_LIST_AN_ISSUES_EVENTS | issue_id |\n| Get event details | SENTRY_RETRIEVE_AN_ISSUE_EVENT | organization_id_or_slug, event_id |\n| List project issues | SENTRY_RETRIEVE_PROJECT_ISSUES_LIST | organization_id_or_slug, project_id_or_slug |\n| List projects | SENTRY_RETRIEVE_ORGANIZATION_PROJECTS | organization_id_or_slug |\n| Get org details | SENTRY_GET_ORGANIZATION_DETAILS | organization_id_or_slug |\n| List teams | SENTRY_LIST_TEAMS_IN_ORGANIZATION | organization_id_or_slug |\n| List members | SENTRY_LIST_ORGANIZATION_MEMBERS | organization_id_or_slug |\n| Create alert rule | SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS | organization_id_or_slug, project_id_or_slug |\n| Create metric alert | SENTRY_CREATE_ORGANIZATION_ALERT_RULE | organization_id_or_slug |\n| Create release | SENTRY_CREATE_RELEASE_FOR_ORGANIZATION | organization_id_or_slug, version |\n| Deploy release | SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORG | organization_id_or_slug, version |\n| List releases | SENTRY_LIST_ORGANIZATION_RELEASES | organization_id_or_slug |\n| Update monitor | SENTRY_UPDATE_A_MONITOR | organization_id_or_slug, monitor_id_or_slug |\n",{"name":5,"requires":49,"description":7},{"mcp":50},[51],"rube","main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Faiskillstore\u002Fmarketplace\u002Fsickn33\u002Fsentry-automation",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill sentry-automation",{"tool":67,"command":68},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill sentry-automation",{"tool":70,"command":71},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill sentry-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fsickn33\u002Fsentry-automation\u002FSKILL.md",true,[75],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"skill-report.json","REFERENCE","参考文档",10209,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fsickn33\u002Fsentry-automation\u002Fskill-report.json",[82,92,101,110,116,123],{"skillNo":83,"name":84,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":88,"publishedAt":44},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[87],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[89,90,91],"model","model hierarchy","model hierarchy skill",{"skillNo":93,"name":94,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":98,"publishedAt":44},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[97],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[28,99,100],"zoom","zoom mcp",{"skillNo":102,"name":103,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":44},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[107,108,109,99],"sdk","zoom apps sdk","apps",{"skillNo":111,"name":112,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":44},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[112],{"skillNo":117,"name":118,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":44},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[121],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[118],{"skillNo":124,"name":125,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":44},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[125]]