[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F4GJ17DRDXSDHSBPPX2X7H":3,"skill-same:01M7F4GJ17DRDXSDHSBPPX2X7H":49},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7F4GJ17DRDXSDHSBPPX2X7H","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fsentry-automation\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fsentry-automation",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill sentry-automation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill sentry-automation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill sentry-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fsentry-automation\u002FSKILL.md",true,[],[50,57,62,69,76,83],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":58,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"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":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]