Token导航 LogoToken导航TokenDH.com
研究检索敏感数据github未标认证来源可访问许可证需确认审计异常

sentry-create-alert哨兵创建警报

Agent Skill

sentry-create-alert 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

23,088

周安装

925

GitHub Stars

156

下载量

7,474
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:sentry-create-alert(哨兵创建警报)
来源仓库:https://github.com/getsentry/sentry-for-ai
仓库路径:skills/sentry-create-alert
安装命令:
npx skills add https://github.com/getsentry/sentry-for-ai --skill sentry-create-alert
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/getsentry/sentry-for-ai --skill sentry-create-alert

简介

用于查找、检索和筛选相关信息,支持关键词驱动的线索定位。

  • 适合在研究或开发中快速获取候选结果和背景资料时调用。
  • 通过 GitHub 安装,配合原始文档理解具体实现逻辑。
  • 需评估是否需要联网及数据访问权限,确保合规使用。
  • sentry-create-alert 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

All Skills > Feature Setup > Create Alert

Create Sentry Alert

Create alerts via Sentry's workflow engine API.

Note: This API is currently in beta and may be subject to change. It is part of New Monitors and Alerts and may not be viewable in the legacy Alerts UI.

Invoke This Skill When

  • User asks to "create a Sentry alert" or "set up notifications"
  • User wants to be emailed or notified when issues match certain conditions
  • User mentions priority alerts, de-escalation alerts, or workflow automations
  • User wants to configure Slack, PagerDuty, or email notifications for Sentry issues

Prerequisites

  • curl available in shell
  • Sentry org auth token with alerts:write scope (also accepts org:admin or org:write)

Phase 1: Gather Configuration

Ask the user for any missing details:

DetailRequiredExample
Org slugYessentry, my-org
Auth tokenYessntryu_... (needs alerts:write scope)
RegionYes (default: us)usus.sentry.io, dede.sentry.io
Alert nameYes"High Priority De-escalation Alert"
Trigger eventsYesWhich issue events fire the workflow
ConditionsOptionalFilter conditions before actions execute
Action typeYesemail, slack, or pagerduty
Action targetYesUser email, team, channel, or service

Phase 2: Look Up IDs

Use these API calls to resolve names to IDs as needed.

API="https://{region}.sentry.io/api/0/organizations/{org}"
AUTH="Authorization: Bearer {token}"

# Find user ID by email
curl -s "$API/members/" -H "$AUTH" | python3 -c "
import json,sys
for m in json.load(sys.stdin):
  if m.get('email')=='USER_EMAIL' or m.get('user',{}).get('email')=='USER_EMAIL':
    print(m['user']['id']); break"

# List teams
curl -s "$API/teams/" -H "$AUTH" | python3 -c "
import json,sys
for t in json.load(sys.stdin):
  print(t['id'], t['slug'])"

# List integrations (for Slack/PagerDuty)
curl -s "$API/integrations/" -H "$AUTH" | python3 -c "
import json,sys
for i in json.load(sys.stdin):
  print(i['id'], i['provider']['key'], i['name'])"

Phase 3: Build Payload

Trigger Events

Pick which issue events fire the workflow. Use logicType: "any-short" (triggers must always use this).

TypeFires when
first_seen_eventNew issue created
regression_eventResolved issue recurs
reappeared_eventArchived issue reappears
issue_resolved_triggerIssue is resolved

Filter Conditions

Conditions that must pass before actions execute. Use logicType: "all", "any-short", or "none".

The comparison field is polymorphic — its shape depends on the condition type:

Typecomparison formatDescription
issue_priority_greater_or_equal75 (bare integer)Priority >= Low(25)/Medium(50)/High(75)
issue_priority_deescalatingtrue (bare boolean)Priority dropped below peak
event_frequency_count{"value": 100, "interval": "1hr"}Event count in time window
event_unique_user_frequency_count{"value": 50, "interval": "1hr"}Affected users in time window
tagged_event{"key": "level", "match": "eq", "value": "error"}Event tag matches
assigned_to{"targetType": "Member", "targetIdentifier": 123}Issue assigned to target
level{"level": 40, "match": "gte"}Event level (fatal=50, error=40, warning=30)
age_comparison{"time": "hour", "value": 24, "comparisonType": "older"}Issue age
issue_category{"value": 1}Category (1=Error, 6=Feedback)
issue_occurrences{"value": 100}Total occurrence count

Interval options: "1min", "5min", "15min", "1hr", "1d", "1w", "30d"

Tag match types: "co" (contains), "nc" (not contains), "eq", "ne", "sw" (starts with), "ew" (ends with), "is" (set), "ns" (not set)

Set conditionResult to false to invert (fire when condition is NOT met).

Actions

TypeKey Config
emailconfig.targetType: "user" / "team" / "issue_owners", config.targetIdentifier: <id>
slackintegrationId: <id>, config.targetDisplay: "#channel-name"
pagerdutyintegrationId: <id>, config.targetDisplay: <service_name>, data.priority: "critical"
discordintegrationId: <id>, data.tags: tag list
msteamsintegrationId: <id>, config.targetDisplay: <channel>
opsgenieintegrationId: <id>, data.priority: "P1"-"P5"
jiraintegrationId: <id>, data: project/issue config
githubintegrationId: <id>, data: repo/issue config

Full Payload Structure

{
  "name": "<Alert Name>",
  "enabled": true,
  "environment": null,
  "config": { "frequency": 30 },
  "triggers": {
    "logicType": "any-short",
    "conditions": [
      { "type": "first_seen_event", "comparison": true, "conditionResult": true }
    ],
    "actions": []
  },
  "actionFilters": [{
    "logicType": "all",
    "conditions": [
      { "type": "issue_priority_greater_or_equal", "comparison": 75, "conditionResult": true },
      { "type": "event_frequency_count", "comparison": {"value": 50, "interval": "1hr"}, "conditionResult": true }
    ],
    "actions": [{
      "type": "email",
      "integrationId": null,
      "data": {},
      "config": {
        "targetType": "user",
        "targetIdentifier": "<user_id>",
        "targetDisplay": null
      },
      "status": "active"
    }]
  }]
}

frequency: minutes between repeated notifications. Allowed values: 0, 5, 10, 30, 60, 180, 720, 1440.

Structure note: triggers.actions is always [] — actions live inside actionFilters[].actions.

Phase 4: Create the Alert

curl -s -w "\n%{http_code}" -X POST \
  "https://{region}.sentry.io/api/0/organizations/{org}/workflows/" \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{payload}'

Expect HTTP 201. The response contains the workflow id.

Phase 5: Verify

Confirm the alert was created and provide the UI link:

https://{org_slug}.sentry.io/monitors/alerts/{workflow_id}/

If the org lacks the workflow-engine-ui feature flag, the alert appears at:

https://{org_slug}.sentry.io/alerts/rules/

Managing Alerts

# List all workflows
curl -s "$API/workflows/" -H "$AUTH"

# Get one workflow
curl -s "$API/workflows/{id}/" -H "$AUTH"

# Update a workflow
curl -s -X PUT "$API/workflows/{id}/" -H "$AUTH" -H "Content-Type: application/json" -d '{payload}'

# Delete a workflow
curl -s -X DELETE "$API/workflows/{id}/" -H "$AUTH"
# Expect 204

Troubleshooting

IssueSolution
401 UnauthorizedToken needs alerts:write scope
403 ForbiddenToken must belong to the target org
404 Not FoundCheck org slug and region (us vs de)
400 Bad RequestValidate payload JSON structure, check required fields
User ID not foundVerify email matches a member of the org

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude

34.82%
按下载量换算2,602

Codex

33.64%
按下载量换算2,514

Cursor

17.78%
按下载量换算1,329

Gemini CLI

10.81%
按下载量换算808

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

未通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills