Datananas

v1.0.0

Datananas integration. Manage data, records, and automate workflows. Use when the user wants to interact with Datananas data.

0· 31·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description (Datananas integration) match the runtime instructions: the skill relies on Membrane CLI to connect to Datananas and run or proxy API actions. No unrelated credentials, binaries, or install steps are requested.
Instruction Scope
SKILL.md instructs installing and using the Membrane CLI, logging in via browser, creating connections, listing actions, running actions, and proxying requests. These steps stay within the integration scope. Note: proxying requests sends API payloads through Membrane's service (expected for the described design) — users should understand that Membrane will see proxied traffic and handle auth.
Install Mechanism
There is no formal install spec in the package registry metadata; the SKILL.md recommends installing @membranehq/cli via npm (global install). This is a standard approach but does require running a third-party npm package globally — verify the package's authenticity and trustworthiness before installing.
Credentials
No environment variables, secrets, or config paths are requested by the skill. The instructions explicitly tell integrators to avoid asking users for API keys and to use Membrane-managed connections instead — this is proportionate to the stated purpose.
Persistence & Privilege
always is false and the skill is user-invocable. The skill does not request elevated platform privileges or permanent presence; autonomous invocation is allowed by default but is not combined with broad credential access here.
Assessment
This skill is coherent: it uses the Membrane CLI to connect to Datananas and does not ask for unrelated credentials. Before installing or using it, verify you trust the Membrane project/@membranehq/cli npm package (review the package on npm and its GitHub repo), and be aware that any proxied API requests and data will pass through Membrane's service (so sensitive data will be visible to that provider). If you prefer not to install a global npm package, use npx or run the CLI in a container. Limit autonomous agent use if you do not want the agent to call the skill without explicit permission.

Like a lobster shell, security has layers — review code before you run it.

latestvk9725wzve0wyzgxbnky7gpnww18479x4

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments