sentry-cli

This is an agent usage guide for the Sentry command line (from getsentry/cli), covering commands for authentication, organizations, projects, issues, events, dashboards, logs, spans, and traces. Most major commands support JSON output. The core rule is to "run commands directly": the CLI automatically identifies the organization and project from configuration files, DSNs in code, and directory names, so do not list organizations before listing projects. You can also use `sentry issue explain` and `sentry issue plan` to invoke Sentry's Seer for issue analysis.

This is an agent usage guide for the Sentry command line (from getsentry/cli), covering commands for authentication, organizations, projects, issues, events, dashboards, logs, spans, and traces. Most major commands support JSON output. The core rule is to "run commands directly": the CLI automatically identifies the organization and project from configuration files, DSNs in code, and directory names, so do not list organizations before listing projects. You can also use sentry issue explain and sentry issue plan to invoke Sentry's Seer for issue analysis.

Why it matters: When troubleshooting production errors, agents can independently retrieve issue details and call chains, and can also invoke Seer to analyze causes and provide fix plans.

skills.sh installs 189181 (+1058 / 24h)

Security Audit: Not audited

  • Not yet scanned

Reasoning

  • skills.sh installs in 24 hours: 1058 (represents attention only)

Usage

  • Ask the agent to check a specific Sentry issue or recent errors; it will run sentry commands directly. If not logged in, the CLI will prompt for login.

Risks

  • Not yet audited; installation commands are not displayed. Requires a Sentry account and permissions for the corresponding project. Seer analysis is billed according to your Sentry plan.

Open · Repository

Best Skills 每日数据(LinklyAI / @BlueeonY,CC BY 4.0)

Explore the latest AI Radar updates