Public agent skills that still call the removed gateway tools (list)

Open
  • Is something wrong?
#2,191 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github, typescript
Domain
developer-experience

Research direction

Read the issue’s list of public agent skill files and the linked discussion in #1952 to understand the gateway removal context. The issue asks whether a list of affected projects would be useful, but does not specify a change to make or how completion would be judged; clarify the desired outcome with maintainers before starting.

Written by the indexing model from the issue text.

Description

#1952 counted 4,853 and 4,047 rejected calls to execute_sentry_tool and search_sentry_tools in the 21 hours after #1868. I looked for where such calls could come from in public code.

  • GitHub code search on November 10 (first 500 results) finds execute_sentry_tool in about 160 repositories outside getsentry.
  • In about 60 of them, an agent skill or instruction file tells the agent to call the gateway by name. I read those files on their default branches.
  • I can't tell whether these account for any of the calls you measured. A mention in a file isn't a call.

I've sent small fixes to three of them so they call the tools directly: ParadevAI/Paradev#9649, go-vikunja/vikunja#4405 and koala73/worldmonitor#10508.

One question: before the gateway is removed for good, would a list like this be useful to you?

Ten of the active projects (file and line)
Project File
koala73/worldmonitor .agents/skills/sentry-triage/SKILL.md, line 25
ParadevAI/Paradev plugins/sentry/skills/debug-with-sentry/SKILL.md, line 5
go-vikunja/vikunja .agents/skills/sentry-triage/SKILL.md, line 18
isHarryh/Ark-Pets .agents/skills/sentry-triage-feedback/SKILL.md, line 95
shopsys/shopsys project-base/.agents/skills/sentry-issue/SKILL.md, line 54
hyvanmielenpelit/GnollHack .agents/skills/sentry_crash_analysis/SKILL.md, line 28
dhis2/dhis2-android-capture-app .claude/skills/sentry-triage/references/sentry-setup.md, line 19
Kilo-Org/cloud .kilo/skills/sentry-mcp/SKILL.md, line 29
CKStudentCouncil/Legislation .claude/skills/fix-sentry-issues/SKILL.md, line 13
FireFightLabs/firefight config/skills/sentry/observability/errors.md, line 4
Dominant language
TypeScript
Stars
961
Forks
179
Avg merge
15h 33m
Merged PRs (30d)
476

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/toolkit

All issues in getsentry/toolkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.