New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Triage Frontend Issues

by getsentry in getsentry/skills

Triage new issues in the Sentry javascript project by archiving non-actionable noise.

OfficialApache-2.0Auto-check passedFrontend & Design

Install Triage Frontend Issues

skills CLI
$ npx skills add getsentry/skills --skill triage-frontend-issues -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install getsentry/skills triage-frontend-issues --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/triage-frontend-issues .claude/skills/triage-frontend-issues && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
triage-frontend-issues
GitHub stars
1k
Token cost
~2k tokens
SKILL.md length
874 words
Files
3 (incl. references)
Skills in repo
27
Repo updated
First seen
Licence
Apache-2.0

At a glance

Triage new issues in the Sentry javascript project by archiving non-actionable noise.

  • Works in 5 steps: Load the queue → Classify each issue → Build the plan → …
  • Asked to triage issues
  • SKILL.md covers Hard Rules, Prerequisites, Inputs and Workflow, plus 2 more sections
  • Reaches sentry.sentry.io

What it does

Triage Frontend Issues is an agent skill from getsentry/skills, published by the product's own GitHub organization. Triage new issues in the Sentry javascript project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", "triage new frontend issues", or "clean up the sentry/javascript queue". Operates only on the sentry/javascript project, only archives (never resolves), and always archives with untilEscalating.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `SPEC.md` and `references/archive-criteria.md`).

It sits in Frontend & Design, covering Issue triage. It works with Sentry, JavaScript and Model Context Protocol. The repository describes itself as: Agent Skills used by the Sentry team for development. The licence is Apache-2.0.

When your agent uses it

  • Asked to triage issues
  • Triage the javascript project
  • Archive non-actionable issues
  • Triage new frontend issues

Example prompts

  • “triage issues”
  • “triage the javascript project”
  • “archive non-actionable issues”
  • “/triage-frontend-issues”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Read, mcp__sentry__search_issues, mcp__sentry__get_sentry_resource, mcp__sentry__update_issue

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Load the queue
  2. Classify each issue
  3. Build the plan
  4. Apply on approval
  5. Report

What it can do on your machine

Read from SKILL.md and the folder at commit d18b7aa. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • mcp__sentry__search_issues
    • mcp__sentry__get_sentry_resource
    • mcp__sentry__update_issue

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • sentry.sentry.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Triage Frontend Issues loads about 2k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 874 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from getsentry/skills at commit d18b7aa, republished under its Apache-2.0 licence (© getsentry). 874 words, ~2,032 tokens.

Download SKILL.mdSave it as .claude/skills/triage-frontend-issues/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
triage-frontend-issues
description
Triage new issues in the Sentry `javascript` project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", "triage new frontend issues", or "clean up the sentry/javascript queue". Operates only on the sentry/javascript project, only archives (never resolves), and always archives with `untilEscalating`.
allowed-tools
Read, mcp__sentry__search_issues, mcp__sentry__get_sentry_resource, mcp__sentry__update_issue

Triage Frontend Issues

Archive non-actionable noise from the sentry/javascript issue queue: only archive, always untilEscalating, always with a stated reason. Issues that look actionable in our code, or that you cannot confidently classify, must be skipped.

Hard Rules

These rules override anything else. Do not relax them.

  1. Project scope. Only operate on organizationSlug=sentry, project slug javascript. If asked to triage a different project, stop and ask the user to confirm.
  2. Archive only. The only status mutation permitted is status=ignored. Never resolve, never unresolve, never assign, never delete, never bulk-update fields other than status.
  3. Always untilEscalating. Use ignoreMode=untilEscalating. Never use forever, forDuration, untilOccurrenceCount, or untilUserCount. If the user asks for a different mode, stop and have them archive that issue manually — this skill does not perform non-escalating archives.
  4. Always include a reason. The reason must be a short, factual sentence naming the category from references/archive-criteria.md (e.g., "Third-party library noise — echarts internals; not actionable in our code").
  5. Never touch issues outside the unresolved queue. Skip anything with status of resolved, ignored, or reprocessing.
  6. Never archive without confirmation. Build a full plan, show it to the user, wait for explicit approval before calling update_issue. A single approval covers the displayed plan only; new batches need new approval.
  7. When in doubt, skip. If an issue could plausibly be a real bug in our code, do not archive it. Surface it as needs-human in the plan with a one-line note.

Prerequisites

  • Sentry MCP authenticated via mcp.sentry.dev. Required tools: search_issues, get_sentry_resource, update_issue.
  • If update_issue is not available, stop and ask the user to authenticate the Sentry MCP server.

Inputs

$ARGUMENTS is one of:

Input shapeMeaning
Sentry issue URL (https://sentry.sentry.io/issues/JAVASCRIPT-…)Triage that single issue.
Issue short ID (JAVASCRIPT-…)Triage that single issue.
Sentry issue query (contains a colon, e.g. is:unresolved firstSeen:-24h)Use as the search query.
EmptyUse the default triage queue: is:unresolved is:unassigned firstSeen:-7d, sort new, limit 50.

If $ARGUMENTS is ambiguous, ask the user to clarify before searching.

Workflow

1. Load the queue

For single-issue input:

  • Call get_sentry_resource(url=<issue-url>) or get_sentry_resource(resourceType='issue', organizationSlug='sentry', resourceId=<shortId>).
  • Confirm Project is the javascript frontend project. If not, stop.

For query/default input:

  • Call search_issues(organizationSlug='sentry', projectSlugOrId='javascript', query=<query>, sort='new', limit=50).
  • Then call get_sentry_resource for each result in parallel to get culprit, substatus, assignee, and stack-frame hints (the search response omits some fields).

Skip immediately if any of these are true on an issue:

  • status is not unresolved (already archived, resolved, or in reprocessing).
  • assignedTo is set to a human (someone is already owning it).
  • assignedTo is set to a team other than frontend/issues and the issue looks team-specific (let the owning team triage).
Show full SKILL.md (437 more words)Show less
2. Classify each issue

Read references/archive-criteria.md for the category taxonomy with recognition heuristics and examples. For each candidate issue, produce one of:

DecisionMeaning
archiveMatches a documented category; include the category name in the reason.
skipCould be a real bug in our code, or insufficient evidence; do not archive.
needs-humanLooks like noise but doesn't cleanly fit a category, or volume is unusually high; flag for user review.

When evaluating, weight these signals (in this order):

  1. Top non-Sentry-SDK frame. If the top in-app frame is in node_modules/, chrome-extension://, a third-party host, or <unknown>, this is a strong archive signal.
  2. Title pattern. Many archives are recognizable from the title alone (see criteria reference).
  3. Volume is not a veto. Some high-volume issues (10k+ events, thousands of users) are still archive-worthy if the top frame is third-party. Volume alone never forces archive either.
  4. Recency. Single-event issues older than 30 days with no recurrence are usually noise.
  5. Customer org spread. If events come from one customer subdomain only (check customerDomain.subdomain tag), it is likely customer-environment noise.
3. Build the plan

Output one Markdown table to the user, in this exact shape:

## Triage plan — sentry/javascript (<N> candidates)

| # | Issue | Title | Volume | Decision | Category | Reason |
|---|-------|-------|--------|----------|----------|--------|
| 1 | [JAVASCRIPT-XXXX](url) | TypeError: ... | 12e/3u | archive | browser-api-noise | Browser clipboard permission denied; not actionable. |
| 2 | [JAVASCRIPT-YYYY](url) | <unknown> | 4945e/123u | needs-human | — | High volume, no title — please review before archiving. |
| 3 | [JAVASCRIPT-ZZZZ](url) | ZodError: ... | 360e/132u | skip | — | Schema validation failure in our code; looks actionable. |

Then summarize counts: N archive / M skip / K needs-human. End with:

Reply `apply` to archive the N issues marked `archive`, `apply N,M,...` to archive a subset, or `cancel` to take no action.
4. Apply on approval

When the user replies apply (or apply <subset>):

For each issue in the approved set, call:

update_issue(
  organizationSlug='sentry',
  issueId=<shortId>,
  status='ignored',
  ignoreMode='untilEscalating',
  reason=<category-tagged reason from the plan>,
)

Run these sequentially (not in parallel). If a call fails, log the failure, continue with the remaining issues, and report the failed IDs in step 5.

If the user replies cancel or asks to modify the plan, do NOT call update_issue. If they reply with edits ("change row 2 to skip"), rebuild the plan and re-confirm.

5. Report

After applying, output:

## Triage report

- Archived: N
- Skipped: M
- Needs human review: K
- Failures: F (with issue IDs)

<details><summary>Archived issues</summary>

- JAVASCRIPT-XXXX — <reason>
- ...

</details>

Recovery

  • If update_issue fails on one item, log the failure and continue with the rest. Report failed IDs at the end.
  • If the user notices a wrong archive, the user can unarchive it themselves in Sentry. The skill never reverses its own actions automatically.
  • If the user asks "redo the plan with these tweaks" mid-flow, regenerate the plan from scratch — do not assume the previous plan still applies.

Example reasons (use this voice)

  • Third-party library noise — echarts tooltip; not actionable in our code.
  • Browser API permission noise — Clipboard writeText denied by user agent.
  • Customer-environment proxy interference — 200 response treated as error (HTML body from corporate proxy).
  • Transient backend 5xx — InternalServerError on /api/0/organizations/.../events-meta/; backend transient.
  • Test/synthetic event — smoke test or security probe, not production traffic.
  • Wrong project — Prisma/Python error mis-routed to frontend project.
  • Single-event fluke — 1 event, 1 user, no recurrence in 30+ days.
  • Browser extension noise — ReferenceError for extension-injected global (DarkReader/WeixinJSBridge).

© getsentry, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/triage-frontend-issues of getsentry/skills.

  • SKILL.md
  • SPEC.md
  • references/archive-criteria.md

Open the folder on GitHubat commit d18b7aa

Compare with similar skills

Triage Frontend Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Triage Frontend Issues compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Triage Frontend Issues this skillgetsentry/skills1k—~2kAutomated safety check: PassApache-2.0
Figma use_figma Plugin API Ruleswarpdotdev/warp65k4 repos~4.4kAutomated safety check: PassAGPL-3.0
Web Performancemozilla/firefox-devtools-mcp470—~1.2kAutomated safety check: PassCustom licence
Servo Fetchkonippi/servo-fetch157—~1.9kAutomated safety check: PassApache-2.0
Golemuigolemui/golemui113—~2.2kAutomated safety check: PassMIT
Sentry Javascript Bugsgetsentry/sentry46k—~2.6kAutomated safety check: NotesCustom licence

Similar skills

  • Figma use_figma Plugin API Rules

    warpdotdev/warp

    Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Frontend & DesignAuto-check passed

  • Web Performance

    mozilla/firefox-devtools-mcp

    Find and fix why a website is slow by capturing and analyzing a Firefox performance profile, or by analyzing a profile the user already has (a saved file or a profiler.firefox.com share link).

    470 GitHub stars~1.2k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • Servo Fetch

    konippi/servo-fetch

    Fetch and render web pages using the Servo browser engine — a single binary with JS execution, CSS layout, screenshots, and content extraction.

    157 GitHub stars~1.9k tokensUpdated 4 days ago
    Frontend & DesignAuto-check passed

  • Golemui

    golemui/golemui

    Build, validate, and debug GolemUI forms in React, Angular, Vue, Lit, or vanilla JS.

    113 GitHub stars~2.2k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Sentry Javascript Bugs

    getsentry/sentry

    Official

    Review Sentry React and TypeScript changes for bug patterns drawn from real production issues.

    46k GitHub stars~2.6k tokensUpdated today
    Frontend & DesignAuto-check: notes

  • Sentry Browser SDK

    getsentry/sentry-for-ai

    Official

    Full Sentry SDK setup for browser JavaScript. An agent skill from getsentry/sentry-for-ai.

    268 GitHub stars~6.5k tokensUpdated today
    Frontend & DesignAuto-check: notes

More from getsentry/skills

All 27 skills in this repo

  • Gh Review Requests

    getsentry/skills

    Official

    Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member.

    1k GitHub starsUsed in 4 repos~621 tokens
    Auto-check: notes

  • Skill Scanner

    getsentry/skills

    Official

    Scan agent skills for security issues. An agent skill from getsentry/skills.

    1k GitHub starsUsed in 4 repos~2.5k tokens
    Auto-check: warnings

  • Security Review

    getsentry/skills

    Official

    Security code review for vulnerabilities. An agent skill from getsentry/skills.

    1k GitHub starsUsed in 4 repos~2.9k tokens
    Auto-check: notes

  • Skill Writer

    getsentry/skills

    Official

    Create, synthesize, and iteratively improve agent skills following the Agent Skills specification.

    1k GitHub stars~2.5k tokensUpdated 5 days ago
    Auto-check passed

  • Django Access Review

    getsentry/skills

    Official

    Django access control and IDOR security review. An agent skill from getsentry/skills.

    1k GitHub starsUsed in 3 repos~2.6k tokens
    Auto-check: notes

  • Gha Security Review

    getsentry/skills

    Official

    GitHub Actions security review for workflow exploitation vulnerabilities.

    1k GitHub starsUsed in 3 repos~2.2k tokens
    Auto-check: notes

Works with

Categories

Questions about Triage Frontend Issues

What does Triage Frontend Issues do?

Triage new issues in the Sentry javascript project by archiving non-actionable noise. Triage Frontend Issues is an agent skill from getsentry/skills, published by the product's own GitHub organization. Triage new issues in the Sentry javascript project by archiving non-actionable noise.

When should I use Triage Frontend Issues?

Triage Frontend Issues fits situations like: asked to triage issues; triage the javascript project; archive non-actionable issues; triage new frontend issues.

How do I install Triage Frontend Issues in Claude Code?

Run `npx skills add getsentry/skills --skill triage-frontend-issues -a claude-code`. Or copy the skill folder (skills/triage-frontend-issues in getsentry/skills) into .claude/skills/triage-frontend-issues in your project. Claude Code loads it when a task matches its description.

How do I install Triage Frontend Issues in Codex?

Run `npx skills add getsentry/skills --skill triage-frontend-issues -a codex`. Or copy the skill folder (skills/triage-frontend-issues in getsentry/skills) into .agents/skills/triage-frontend-issues in your project. Codex loads it when a task matches its description.

Can I use Triage Frontend Issues in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getsentry/skills --skill triage-frontend-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triage-frontend-issues, .gemini/skills/triage-frontend-issues, .github/skills/triage-frontend-issues and .opencode/skills/triage-frontend-issues in your project.

What does Triage Frontend Issues need to run?

SKILL.md names no scripts, command-line tools or credentials: Triage Frontend Issues is instructions for the agent only. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, mcp__sentry__search_issues, mcp__sentry__get_sentry_resource, mcp__sentry__update_issue.

Does Triage Frontend Issues access the network?

SKILL.md names 1 domain. In commands or code: sentry.sentry.io; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Triage Frontend Issues safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Triage Frontend Issues use?

Triage Frontend Issues is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Triage Frontend Issues use?

About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.

What are the alternatives to Triage Frontend Issues?

Skills that share tags, products or a category with Triage Frontend Issues: Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars), Web Performance (mozilla/firefox-devtools-mcp, 470 stars), Servo Fetch (konippi/servo-fetch, 157 stars) and Golemui (golemui/golemui, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Triage Frontend Issues?

getsentry (a GitHub organization, an official publisher) maintains it in getsentry/skills, which has 1,038 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 2, 2026.

Source: getsentry/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.