Sentry Observability

v1.1.0

Add observability to your OpenClaw instance — errors, logs, and traces sent to Sentry. Set up monitoring with the Sentry plugin, then investigate issues with...

0· 842·1 current·1 all-time
bySergiy Dybskiy@sergical
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name/description (Sentry observability) aligns with the actions described (configure DSN, enable plugin, use sentry CLI and SDK). However the SKILL.md expects tools and runtimes beyond the single declared binary: it uses npm, Node packages (@sentry/node, @sentry/core), and shell tools like jq, none of which are listed in the registry metadata's required binaries. That mismatch is unexpected and should be clarified.
Instruction Scope
Runtime instructions stay within the stated purpose: authenticating to Sentry, creating a project, adding a DSN to openclaw.json, installing a plugin, and using the sentry CLI and API to inspect issues/logs/traces. The instructions do reference storing credentials in ~/.sentry/cli.db and suggest using SENTRY_AUTH_TOKEN, which is typical for Sentry CLI usage but is not declared in requires.env.
!
Install Mechanism
Registry metadata said 'No install spec', but the SKILL.md metadata includes an npm install entry (global 'sentry' package). This inconsistency is concerning. Installing a global npm package is a moderate-risk action because npm packages can execute code; the skill does not point to a clearly verified release host for the CLI install. Also the SKILL.md and references expect adding Node SDK dependencies (@sentry/node and @sentry/core) to a plugin—these steps require npm and a Node runtime but npm/node are not declared as required binaries.
Credentials
The skill does not declare required environment variables in registry metadata, but the instructions discuss SENTRY_AUTH_TOKEN as an auth alternative and instruct running 'sentry auth login' which stores credentials in ~/.sentry/cli.db. Requesting a Sentry DSN and an auth token is proportionate to the stated purpose, but the SKILL.md referencing SENTRY_AUTH_TOKEN without declaring it is an inconsistency to surface to users.
Persistence & Privilege
The skill does not request persistent 'always' inclusion or elevated platform privileges. The only persistent side effects described are normal for this integration: creating a Sentry project, storing CLI credentials under the user's home (~/.sentry/cli.db), and adding plugin config to openclaw.json. Nothing indicates modification of other skills or system-wide settings beyond that scope.
What to consider before installing
This appears to be a legitimate Sentry integration, but check a few things before installing: - Confirm the CLI install source: SKILL.md suggests 'npm install -g sentry' (in its metadata). Verify that the npm package named 'sentry' is the official Sentry CLI; if uncertain, prefer the official install method from https://cli.sentry.dev or an official package (installing arbitrary global npm packages can run code on your system). - The skill's instructions use npm, Node SDKs (@sentry/node, @sentry/core) and the jq tool, but the registry metadata only listed the 'sentry' binary. Ensure you have npm/node/jq available, and be comfortable with the plugin installing Node dependencies. - The instructions refer to SENTRY_AUTH_TOKEN (and storing credentials in ~/.sentry/cli.db). Treat DSNs and auth tokens as secrets—only supply tokens you trust this integration with, and consider using a least-privilege token for CI or automation. - The SKILL.md includes an 'install' entry in its metadata even though the registry noted no install spec—ask the publisher or maintainer to clarify the intended install flow and the exact packages/URLs used. - If you want to be cautious, inspect the plugin source at the referenced GitHub repo (https://github.com/sergical/openclaw-plugin-sentry) before enabling it, or implement Sentry using the official CLI/SDK install instructions rather than an unknown npm package. If you want, I can: (a) list the exact commands the skill would run, (b) draft a safer install checklist using official Sentry install methods, or (c) try to validate whether the npm package 'sentry' is the official CLI (you would need to permit me to check external package metadata or provide it).

Like a lobster shell, security has layers — review code before you run it.

latestvk97ct76qqhxa18h5exrdk0q8jn81atbs

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🐛 Clawdis
Binssentry

Comments