Sentry Cli

Sentry.io error monitoring via sentry-cli. Use when working with Sentry releases, source maps, dSYMs, events, or issue management. Covers authentication, release workflows, deploy tracking, and debug file uploads.

This SKILL.md is a legitimate how-to for sentry-cli, but take these precautions before installing or using it: 1) The skill metadata lists no source or homepage — verify the publisher before trusting it. 2) The instructions use sensitive values (SENTRY_AUTH_TOKEN, SENTRY_ORG, SENTRY_PROJECT) even though the registry did not declare required credentials — only provide a token with the minimum scope needed (prefer a CI-specific token), and avoid placing high-privilege tokens in global env. 3) Prefer installing sentry-cli via your platform's package manager (brew or npm) rather than blindly running curl | bash; if you must use the installer script, inspect it first. 4) Be aware the commands may read and upload local artifacts or logs (dSYMs, /var/log/app.log, build artifacts) — review what will be uploaded. 5) If you allow autonomous agent invocation, restrict when the skill can run and monitor token usage. If you want, request the skill author to declare required env vars and provide a verifiable homepage/source before proceeding.

Type: OpenClaw Skill Name: sentry-cli Version: 1.0.1 The skill bundle is designed to interact with the legitimate Sentry.io CLI. However, the `SKILL.md` documentation includes an installation method for `sentry-cli` using `curl -sL https://sentry.io/get-cli/ | bash`. While this is a common and officially documented installation method for `sentry-cli`, it inherently involves executing arbitrary code downloaded from a remote server, which is a high-risk practice and a potential supply chain vulnerability if the remote server were ever compromised. There is no evidence of intentional malicious behavior or prompt injection attempts against the agent beyond the stated purpose.