Seqera
v1.0.2Seqera integration. Manage Organizations, Users, Pipelines. Use when the user wants to interact with Seqera data.
⭐ 0· 72·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
Name/description (Seqera integration) match the instructions: the SKILL.md explains using Membrane CLI to manage Seqera Organizations, Users, Pipelines and to proxy requests to Seqera. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions are specific and scoped to installing and using the @membranehq/cli (login, create connections, list/run actions, proxy requests). They do not instruct reading unrelated system files, environment variables, or exfiltrating data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill that asks users to install the Membrane CLI via npm (npm install -g @membranehq/cli) and shows npx usage. Installing an npm package globally is a reasonable and expected install route here, but npm package installation can execute code on the host — verify package provenance (publisher, npm page, repository) before installing. Using npx or a local install can reduce host-wide impact.
Credentials
The skill requests no environment variables or credentials and explicitly directs using Membrane connections rather than asking for API keys. Required access (network + Membrane account) is proportional and documented.
Persistence & Privilege
Skill is not always-enabled and does not request elevated permanence. It is user-invocable and uses external CLI tooling; autonomous invocation is platform-default and not excessive here.
Assessment
This skill is coherent: it uses the Membrane CLI to access Seqera and asks for no extra credentials. Before installing: (1) verify the @membranehq/cli package on npm (publisher, repo, recent releases) to ensure you trust the package; (2) consider using npx or a local install rather than a global -g install to limit system-wide effects; (3) run the CLI in an environment with appropriate network and account permissions (Membrane handles auth server-side so you don't need to hand over API keys). If you want tighter control, test the CLI in a sandbox or container first.Like a lobster shell, security has layers — review code before you run it.
latestvk974j1v09sqjkhq833j9yjy5cn843kax
License
MIT-0
Free to use, modify, and redistribute. No attribution required.