getsentry / cli

getsentry/cli is the CLI itself: authentication, issue triage, releases, source maps, dashboards, and monitors, installable via a curl script, Homebrew, or npm/pnpm/yarn/bun (the npm route needs Node 22.15+), plus a TypeScript library for calling it programmatically instead of spawning a subprocess. The one skill it ships, sentry-cli, is backed by 31 separate reference files, one per command area — auth, issue, release, sourcemap, monitor, dashboard, trace, and 24 more — so an agent reading it gets the CLI's full command surface rather than a short cheat sheet.

This is for teams already sending errors to Sentry who want their coding agent driving the CLI directly — listing and triaging issues, pulling Seer's AI-generated root-cause analysis and fix plans, or scripting releases and source-map uploads. There is nothing here for an agent to learn that isn't a Sentry command; without a Sentry account there is no reason to install it.

READ THE FULL ANALYSIS＋

What we can't confirm from the file itself. The scrape of sentry-cli's own top-level SKILL.md returned only a relative path — ../../../plugins/sentry-cli/skills/sentry-cli/SKILL.md — not the prose an agent actually reads before it opens one of the 31 references. Those 31 reference files are real and named for real CLI areas, but we can't independently show what top-level instruction sends an agent to the right one.