Sedna
v1.0.0SEDNA integration. Manage data, records, and automate workflows. Use when the user wants to interact with SEDNA data.
⭐ 0· 71·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 (Sedna integration) match the instructions: all steps show how to discover connectors, create a Sedna connection, run actions, or proxy requests via the Membrane CLI. Nothing requested is unrelated to interacting with Sedna data.
Instruction Scope
SKILL.md stays on task: it tells the agent to install and use the Membrane CLI, run login/connect/action/request commands, and how to handle headless auth. It does not instruct reading arbitrary system files or exporting unrelated environment variables.
Install Mechanism
The skill is instruction-only (no install spec). It tells users to install @membranehq/cli via npm (or use npx). Installing a global npm CLI runs third‑party code on the host — expected for this integration but a non-trivial trust decision. The guidance to use npx in places is safer than recommending a global install everywhere.
Credentials
The skill requests no env vars or host credentials itself. However, it relies on Membrane to manage authentication and to proxy requests to Sedna — this means sensitive data and API calls will be routed through Membrane's service, so you must trust that third party with any data you send.
Persistence & Privilege
The skill does not request persistent or cross-skill privileges (always:false). It doesn't attempt to modify other skill configurations or system-wide settings. Any persistence would come from the CLI the user chooses to install, not from the skill bundle.
Assessment
This skill is coherent for connecting to Sedna via the Membrane platform, but before installing or using it: 1) Review the @membranehq/cli npm package (package page, maintainer reputation, recent releases) or prefer using npx to avoid a global install. 2) Understand that Membrane will proxy requests and manage auth — any data sent to Sedna via this flow will also transit through Membrane; confirm this meets your privacy/compliance needs. 3) When running membrane login/connect, inspect the browser auth prompts and the connector scopes. 4) If you need stronger assurance, check the upstream repo (https://github.com/membranedev/application-skills) and the vendor site (https://getmembrane.com) for docs and source; consider testing in a sandbox environment first. 5) Because the skill is instruction-only, the registry does not ship code — installing the CLI is a manual step and therefore a separate trust decision.Like a lobster shell, security has layers — review code before you run it.
latestvk97bfnndghtd2awj6gdjq19yg1845xxk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.