Agent skill

Triage Monitoring Event

by blockscout in blockscout/frontend

Triage one error-monitoring event end-to-end — mute it as noise, or open a PR with the fix.

Custom licenceAuto-check passedDevelopment

Install Triage Monitoring Event

skills CLI
$ npx skills add blockscout/frontend --skill triage-monitoring-event -a claude-code

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

GitHub CLI
$ gh skill install blockscout/frontend triage-monitoring-event --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/blockscout/frontend.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/triage-monitoring-event .claude/skills/triage-monitoring-event && 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-monitoring-event
GitHub stars
307
Token cost
~1.7k tokens
SKILL.md length
1,092 words
Files
2
Skills in repo
24
Repo updated
First seen
Licence
Custom licence

At a glance

Triage one error-monitoring event end-to-end — mute it as noise, or open a PR with the fix.

  • Works in 6 steps: Resolve the input → Check the tool → Read the event → …
  • Tasks that involve Pull requests
  • SKILL.md covers Steps and Run by Honk
  • Calls git

What it does

Triage Monitoring Event is an agent skill from blockscout/frontend. Triage one error-monitoring event end-to-end — mute it as noise, or open a PR with the fix.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `rollbar.md`).

It sits in Development, covering Pull requests. The repository describes itself as: Front-end application for Blockscout chain explorer.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/triage-monitoring-event”

Workflow steps

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

  1. Resolve the input
  2. Check the tool
  3. Read the event
  4. Locate the code
  5. Classify
  6. Report

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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 Monitoring Event loads about 1.7k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 1,092 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,092 words (~1,713 tokens).

“One event in, one of three outcomes out: the event is muted in the monitoring tool, a PR with the fix is open, or the event is reported as already fixed on main, with the commit named. The mute and…”

— opening of SKILL.md by blockscout, Custom licence
name
triage-monitoring-event
disable-model-invocation
true
argument-hint
<event URL or id, or a Slack message/thread link carrying one>

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in .agents/skills/triage-monitoring-event of blockscout/frontend.

  • SKILL.md
  • rollbar.md

Open the folder on GitHubat commit 56ff467

Compare with similar skills

Triage Monitoring Event 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 Monitoring Event compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Triage Monitoring Event this skillblockscout/frontend307—~1.7kAutomated safety check: PassCustom licence
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands91k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    91k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from blockscout/frontend

All 24 skills in this repo
  • Slack File

    blockscout/frontend

    Download Slack attachments by file ID, or upload local files into a Slack thread.

    307 GitHub stars~540 tokensUpdated yesterday
    Auto-check passed
  • Add Env Var

    blockscout/frontend

    Step-by-step checklist for adding a new NEXTPUBLIC environment variable.

    307 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check: notes
  • Add New Page

    blockscout/frontend

    Scaffold a new page (index / detail / general) and optionally wire it to API data.

    307 GitHub stars~3.9k tokensUpdated yesterday
    Auto-check passed
  • Create Issue

    blockscout/frontend

    Create a GitHub issue from the available context. An agent skill from blockscout/frontend.

    307 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Deprecate Env Var

    blockscout/frontend

    Checklist for deprecating a NEXTPUBLIC environment variable — immediate removal, or a grace period before a later removal.

    307 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check: notes
  • Publish Beta Types

    blockscout/frontend

    Publish a beta version of a @blockscout/-types npm package and pin it here.

    307 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Triage Monitoring Event

What does Triage Monitoring Event do?

Triage one error-monitoring event end-to-end — mute it as noise, or open a PR with the fix. Triage Monitoring Event is an agent skill from blockscout/frontend. Triage one error-monitoring event end-to-end — mute it as noise, or open a PR with the fix.

When should I use Triage Monitoring Event?

Triage Monitoring Event fits situations like: tasks that involve Pull requests.

How do I install Triage Monitoring Event in Claude Code?

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

How do I install Triage Monitoring Event in Codex?

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

Can I use Triage Monitoring Event 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 blockscout/frontend --skill triage-monitoring-event -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-monitoring-event, .gemini/skills/triage-monitoring-event, .github/skills/triage-monitoring-event and .opencode/skills/triage-monitoring-event in your project.

What does Triage Monitoring Event need to run?

Going by SKILL.md and its folder, Triage Monitoring Event needs the command-line tools its instructions call (git).

Does Triage Monitoring Event access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Triage Monitoring Event 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 Monitoring Event use?

Triage Monitoring Event has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Triage Monitoring Event use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Triage Monitoring Event?

Skills that share tags, products or a category with Triage Monitoring Event: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 91k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Triage Monitoring Event?

blockscout (a GitHub organization) maintains it in blockscout/frontend, which has 307 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 9, 2026.

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