Nlp Cloud
v1.0.0NLP Cloud integration. Manage data, records, and automate workflows. Use when the user wants to interact with NLP Cloud data.
⭐ 0· 22·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
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (NLP Cloud integration) matches the instructions: the SKILL.md shows how to use the Membrane CLI to connect to NLP Cloud, list actions, run actions, and proxy API requests. Required capabilities (network access and a Membrane account) are appropriate for this purpose.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, authenticating via browser, creating connections, listing/running actions, and proxying requests through Membrane. That stays within the stated purpose. Note: the proxy capability lets you send arbitrary API requests via Membrane — this is expected for an integration but is a powerful capability that will relay requests to external endpoints.
Install Mechanism
There is no bundled install spec; the SKILL.md instructs the user to run `npm install -g @membranehq/cli`. Installing a global npm package is common for CLIs but grants execution capability from that package, so users should verify the package and publisher before installing globally.
Credentials
The skill declares no required environment variables or local credentials. It explicitly directs credential handling to Membrane (server-side) and advises not to ask users for API keys, which is proportionate to the stated purpose.
Persistence & Privilege
The skill is not force-included (always: false) and does not request persistent agent privileges or modify other skills. It requires user-invocation and browser-based authentication flows, which are appropriate for this integration.
Assessment
This skill is coherent and appears to do what it says: use Membrane to interact with NLP Cloud. Before installing or following the instructions: (1) verify you trust the Membrane project and the npm package (@membranehq/cli) — check the maintainer, package popularity, and repository; (2) prefer installing the CLI in a controlled environment (not a production server) until you confirm behavior; (3) be aware that Membrane will proxy arbitrary API requests on your behalf and will handle credentials server-side — ensure you are comfortable delegating auth to that service; (4) review any output that contains connection IDs or tokens and revoke connections from the Membrane dashboard if suspicious. If you want higher assurance, inspect the CLI source on the referenced repository before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97car8pcbnhj0gcpkza6cp09d84dg7b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.