[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSRG8J060GZTQRRN6DFQRN":3,"skill-same:01M6FSRG8J060GZTQRRN6DFQRN":75},{"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":53,"commitSha":54,"skillDirectory":55,"forksCount":14,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6FSRG8J060GZTQRRN6DFQRN","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.","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\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","community","manage","releases","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]\nrisk: unknown\nsource: community\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\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\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\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":49,"source":32,"requires":50,"description":7},"unknown",{"mcp":51},[52],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Fsentry-automation","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add reikiplanet\u002Fdaoskills --skill sentry-automation",{"tool":67,"command":68},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill sentry-automation",{"tool":70,"command":71},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill sentry-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fsentry-automation\u002FSKILL.md",true,[],[76,102,114,128,148,171],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":44},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[83,84,85,86,87,88,32,89,90,91,92,93,94,95,96,97,98,99,100,101],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":44},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[109,110,100,111,112,32,90,91,92,86,113,87],"ar","vr ar","interaction","requirements","performance",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":44},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[116,121,122,123,124,125,32,126,92,35,127,86],"project scaffolding","From Scratch","tech","project","scaffolding","use","applications",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":44},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[135,136,137,138,139,32,140,141,142,143,126,144,145,146,147],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":44},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[155,156,157,158,159,160,161,162,32,92,86,163,87,164,165,166,167,168,169,170],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":44},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[178,179,180,181,182,183,184,185,168,126,186,187,188,32,189,190,191,165,192,193],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]