Sentry Error Triage

Sentry error tracking — list, triage, and resolve issues; manage releases and source maps via CLI and REST API.

This skill appears to implement Sentry triage correctly, but there are a few red flags you should address before installing: (1) The SKILL.md requires SENTRY_AUTH_TOKEN, SENTRY_ORG, and SENTRY_PROJECT, but the skill metadata does not declare these — assume the skill will need a Sentry token with the scopes it lists. Only provide a token with the minimum scopes and avoid long-lived or org-wide tokens if possible. (2) The instructions tell the agent to read local code files to suggest fixes. If you enable this skill, limit the agent's filesystem access (run it in a repo-limited workspace or sandbox) so it can't read unrelated files. (3) Installation guidance recommends global npm/pip installs; prefer installing sentry-cli from an official package manager in a controlled environment (or use a container/virtualenv) to avoid polluting system-wide binaries. (4) Verify the skill author/origin before use — there is no homepage or publisher information. If you need higher confidence, ask the publisher to update the skill metadata to explicitly declare required env vars and installation steps, or perform manual triage via your own Sentry CLI/REST scripts rather than granting the skill live access.

Type: OpenClaw Skill Name: sentry-error-triage Version: 1.0.0 The skill provides a standard integration for Sentry error tracking, allowing an agent to list, triage, and resolve issues using the official `sentry-cli` and REST API. The instructions in `SKILL.md` are well-documented, focusing on legitimate operational workflows such as release management and source map uploads. There are no signs of data exfiltration, malicious execution, or suspicious network activity, as all API calls are directed to the official `sentry.io` domain.