Signal Sciences
v1.0.2Signal Sciences integration. Manage data, records, and automate workflows. Use when the user wants to interact with Signal Sciences data.
⭐ 0· 50·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 README describes a Signal Sciences integration implemented via the Membrane platform. Requiring the Membrane CLI and a Membrane account matches that stated purpose; there are no unrelated env vars, binaries, or config paths requested.
Instruction Scope
SKILL.md instructs installing and using the Membrane CLI, logging in, creating a connector, listing actions, running actions, and proxying requests to Signal Sciences. It does not instruct reading unrelated local files or harvesting other credentials; it explicitly says not to ask users for API keys.
Install Mechanism
The skill is instruction-only and asks users to install @membranehq/cli via npm -g. That is a reasonable, traceable install path, but installing global npm packages runs third-party code on the host — users should verify the package source and trustworthiness of @membranehq before installing.
Credentials
The skill requests no environment variables or credentials and delegates auth to Membrane. This is proportionate for a connector-based integration; the instructions emphasise using Membrane-managed connections rather than local secrets.
Persistence & Privilege
The skill is not always-enabled and doesn't request elevated or cross-skill configuration changes. It relies on the Membrane CLI and normal browser-based authentication flows; autonomous model invocation remains enabled by platform default but is not combined with other concerning privileges here.
Assessment
This skill delegates Signal Sciences access to the Membrane platform and tells you how to install and use the Membrane CLI. Before installing: (1) Verify you trust Membrane/@membranehq (the skill will ask you to install their npm CLI and to authenticate via browser), (2) prefer creating a limited-scope Signal Sciences connection/account for automation rather than using full-admin credentials, (3) note that Membrane will proxy arbitrary API requests you instruct it to make — be careful what actions you run, and (4) installing global npm packages executes third-party code on your machine, so inspect the package and prefer installation in a controlled environment if you have concerns. Autonomous agent invocation is platform-default; if you do not want the agent to call this skill without explicit confirmation, adjust agent invocation settings.Like a lobster shell, security has layers — review code before you run it.
latestvk97dgsswm6qkz6ycs194kyszan843q0t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.