Sentry
v1.0.0Sentry API integration with managed authentication. Monitor errors, issues, and application performance. Use this skill when users want to list issues, retri...
⭐ 0· 387·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (Sentry API integration) matches the runtime instructions: all example requests target a Maton gateway that proxies to Sentry. Requesting a MATON_API_KEY is coherent for a managed-gateway approach. There are no unrelated env vars or binaries requested.
Instruction Scope
SKILL.md instructs the agent to make HTTP requests to https://gateway.maton.ai and control calls to https://ctrl.maton.ai, and to include Authorization: Bearer $MATON_API_KEY. It also suggests opening OAuth URLs in a browser to complete authorization. The instructions do not ask the agent to read arbitrary local files, other env vars, or other system state. Note: using a third-party gateway means requests (and potentially Sentry data) will transit Maton's infrastructure.
Install Mechanism
There is no install spec and no code files beyond SKILL.md; this is instruction-only so nothing is written to disk by the skill itself.
Credentials
Only a single env var (MATON_API_KEY) is required, which is proportionate to a gateway-based integration. However, that single key likely grants Maton access to your Sentry data (and to manage connections), so the key is powerful — verify its scope and trust the Maton operator before supplying it.
Persistence & Privilege
The skill does not request always:true, does not install persistent components, and does not modify other skills or system-wide settings. Agent autonomous invocation is allowed but is the platform default and not a special privilege here.
Assessment
This skill appears to do what it says: it routes Sentry API calls through Maton and requires a single MATON_API_KEY. Before installing or using it: 1) Confirm you trust maton.ai as a gateway operator — requests and Sentry data will transit their infrastructure. 2) Check what scopes/permissions the MATON_API_KEY grants and prefer least-privilege / read-only keys for testing. 3) If you prefer not to route data through a third party, consider using direct Sentry API tokens instead. 4) Store the MATON_API_KEY securely (secret manager / environment only) and be prepared to rotate/revoke it if needed. 5) Verify the publisher identity (registry shows unknown source/homepage mismatch) before granting access to production data.Like a lobster shell, security has layers — review code before you run it.
latestvk976ttef0m73ww70wjr5fnyd6581pped
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🧠 Clawdis
EnvMATON_API_KEY