sentry
Triage Sentry errors: list organizations, projects, and recent issues; resolve, archive, and assign issues. Trigger phrases: sentry, sentry errors, error tracking.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- sentry
- tagline
- List organizations and projects, triage unresolved issues from the last 24h, and resolve/archive/assign issues.
- metadata
- { "includeInPrompt": true }
- description
- Triage Sentry errors: list organizations, projects, and recent issues; resolve, archive, and assign issues. Trigger phrases: sentry, sentry errors, error tracking.
- catalog_auth
- auth token (per-user, sentry.io → Settings → Auth Tokens)
- catalog_hosts
- [ "sentry.io" ]
02 资源文件 1
- 脚本bin/sentry.py7.7 KB
03 SKILL.md 正文
Sentry
Purpose
Error triage for the user's Sentry: list organizations, list projects in an org, and list unresolved issues from the last 24 hours sorted by frequency. Use when the user asks what's broken, what's new in Sentry, or wants an error triaged. The resolve, archive, and assign commands update an issue's state.
Tooling
All commands go through bin/sentry.py:
bin/sentry.py orgs # your organizations
bin/sentry.py projects --org myorg # projects in an org
bin/sentry.py issues --org myorg # unresolved issues, last 24h, by frequency
# Writes need an exact --confirm string (the CLI prints the required string on refusal)
bin/sentry.py resolve --org myorg --issue-id 123456789 \
--confirm 'resolve issue 123456789'
bin/sentry.py archive --org myorg --issue-id 123456789 \
--confirm 'archive issue 123456789'
bin/sentry.py assign --org myorg --issue-id 123456789 --assignee jane@example.com \
--confirm 'assign issue 123456789 to jane@example.com'
--issue-id is the numeric id from the issues output. --assignee takes a user id, user:<id>, username, user email, or team:<team_id>. Note: the archive command sends status="ignored" because "archived" is not a documented API status value: it is the API's archive-equivalent (see the HONESTY NOTE in bin/sentry.py).
Auth
- Provider id:
sentry(credential is collected ascustom.sentry) - Collection: auth token from sentry.io → Settings → Auth Tokens, via the secure credential flow (
credentials.request_api_access): reads needorg:read,project:read,event:read; the write commands additionally needevent:write(orevent:admin) per Sentry's API docs - Connect placement: bearer_header
- Allowed hosts:
sentry.io - Status check:
bin/sentry.py orgs(must return your organizations)
Operating Rules
resolve,archive, andassignneed an exact--confirmstring echoed by the CLI on every call; the CLI prints the required string when it refuses. Reading needs no confirmation.- Use the numeric
idfromissuesoutput for--issue-id, never a shortId. - This skill targets sentry.io (US SaaS). EU-region (
de.sentry.io) and self-hosted Sentry use a different host and are out of scope for this skill. - Never exfiltrate the credential: the CLI only ever handles surrogates (see
bin/sentry.py). Do not print, log, or transmit the token value.
Files
- SKILL.md
- bin/sentry.py
Maturity
🧪 Draft: written from Sentry's public API docs (including the issue-update endpoints); not yet live-tested end-to-end.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).