Appsignal
v1.0.2AppSignal integration. Manage data, records, and automate workflows. Use when the user wants to interact with AppSignal data.
⭐ 0· 96·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description promise AppSignal integration and the SKILL.md consistently instructs using the Membrane CLI to connect, list actions, run actions, and proxy requests to AppSignal. Required capabilities (network access and a Membrane account) match the stated purpose.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, authenticating via the browser or headless flow, creating/listing connections, invoking actions, and proxying requests. The instructions do not ask the agent to read unrelated files or environment variables, nor to exfiltrate data to unknown endpoints.
Install Mechanism
No registry install spec exists (instruction-only), but the SKILL.md recommends 'npm install -g @membranehq/cli' (a public npm package). This is a normal install path for a CLI but has moderate risk compared with no-install skills — verify the npm package publisher and prefer using npx when possible to avoid global installs.
Credentials
The skill requests no environment variables or secrets. Authentication is delegated to Membrane via an interactive browser flow; this is proportionate to the task. Note: using Membrane means the service will handle credentials server-side, so review Membrane's privacy/security policies if you care about data residency.
Persistence & Privilege
The skill does not request persistent/always-on presence (always:false) and does not instruct modifying other skills or system-wide settings. Autonomous invocation is allowed (platform default) but not combined with other high-risk factors.
Assessment
This skill is internally consistent: it tells the agent to use the Membrane CLI to access AppSignal and does not ask for unrelated secrets. Before installing or running commands: 1) verify the npm package '@membranehq/cli' publisher and consider using 'npx' instead of a global 'npm install -g' to avoid privileged global installs; 2) be aware that Membrane acts as a proxy and will see requests and potentially sensitive telemetry — review Membrane's privacy/security docs and your organization's policy on routing telemetry through third parties; 3) the login flow opens a browser (or provides a URL/code for headless use), so do not paste sensitive tokens into untrusted consoles; and 4) if you need a higher assurance level, request the skill author/publisher or a checksum for the CLI package and confirm the homepage/repository URLs independently.Like a lobster shell, security has layers — review code before you run it.
latestvk9728rhxr15bvtzb170p15c0tx843vsw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.