Translatecom
v1.0.0Translate.com integration. Manage data, records, and automate workflows. Use when the user wants to interact with Translate.com data.
⭐ 0· 60·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 and runtime instructions align: the skill uses the Membrane CLI to connect to Translate.com, list/run actions, and proxy API requests. It does not ask for unrelated credentials or system access.
Instruction Scope
SKILL.md stays within the Translate.com integration scope (install Membrane CLI, perform browser login, create connections, list/run actions, and proxy requests). Note: the proxy/run commands permit arbitrary API requests to Translate.com via Membrane, which is expected for this use case but grants broad ability to transmit user data to the Membrane service and Translate.com.
Install Mechanism
There is no registry install spec; the doc instructs the user to run npm install -g @membranehq/cli. This is a public npm package (traceable) but a global npm install modifies the host environment and is higher-impact than an instruction-only skill that requires no installs.
Credentials
The skill requests no local environment variables or secrets and explicitly instructs not to ask users for API keys; authentication is handled via Membrane (server-side). This is proportionate, but it requires trusting Membrane to store/manage credentials.
Persistence & Privilege
The skill does not request persistent or elevated platform privileges (always:false). It is user-invocable and can be invoked autonomously by the agent (normal behavior) but does not modify other skills or system-wide settings.
Assessment
This skill appears internally consistent, but before installing: 1) Confirm you trust Membrane (getmembrane.com) because Membrane will hold credentials and proxy requests to Translate.com. 2) Review the @membranehq/cli npm package and its source (GitHub) before running a global npm install, or install it in an isolated/containerized environment if you prefer. 3) Be aware that the "membrane request" and action-run commands can send arbitrary data to Membrane/Translate.com—do not forward sensitive secrets or unrelated files. 4) If you're on a shared machine, avoid global installs or use a per-project/node environment. 5) If you need higher assurance, ask the skill author for a signed repository link or inspect the CLI source/code before use.Like a lobster shell, security has layers — review code before you run it.
latestvk979df6mm0n7d8estqz1ry2z4584ah3h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.