Dyn
v1.0.2Dyn integration. Manage data, records, and automate workflows. Use when the user wants to interact with Dyn data.
⭐ 0· 47·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 (Dyn integration) aligns with the instructions: all runtime actions are performed via the Membrane CLI which proxies to Dyn. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md tells the agent to install and use @membranehq/cli, run connector discovery, create connections, run actions, and proxy arbitrary Dyn API requests through Membrane. These are within scope for a Dyn integration, but the proxy capability means the CLI can issue arbitrary API calls on your behalf — expected for this type of integration but worth being aware of.
Install Mechanism
No formal install spec in registry metadata; SKILL.md asks you to run `npm install -g @membranehq/cli` and references `npx`. Installing a global npm CLI is a common way to get a CLI, but it does run third-party code on your machine and carries the usual risks of installing packages from npm. This is proportionate to the stated functionality but verify package provenance (organization, npm page, GitHub repo/signatures) before installing.
Credentials
The skill declares no required env vars, no config paths, and no local secrets. It delegates authentication to Membrane (server-side), which is appropriate for this integration. Note: delegating auth means Membrane will hold/refresh your Dyn credentials—ensure you trust that service.
Persistence & Privilege
The skill is not forced-always, does not request elevated platform privileges, and is instruction-only (no code written by installer). Autonomous invocation is allowed (platform default) but is not combined with other high-risk factors here.
Assessment
This skill appears to do what it says: it requires installing and using the Membrane CLI to connect to Dyn. Before installing or using it, verify you trust Membrane (https://getmembrane.com / the referenced GitHub repo) because the service will hold Dyn credentials and can proxy arbitrary API calls. Also confirm the npm package author and package page, and prefer using npx or a non-global install if you want to limit system-wide changes. If you need to run this on a headless or production system, review how Membrane manages credentials and consider least-privilege Dyn credentials or an audit of actions allowed by the connector.Like a lobster shell, security has layers — review code before you run it.
latestvk977xaqsndd82my5c41ph44q6s842raf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.