Textlocal
v1.0.2Textlocal integration. Manage data, records, and automate workflows. Use when the user wants to interact with Textlocal data.
⭐ 0· 120·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
medium confidencePurpose & Capability
The skill is described as a Textlocal integration and all instructions center on using Membrane's CLI to connect to Textlocal and run actions. Required tools and steps (membrane CLI, login, connector usage) are coherent with the stated purpose.
Instruction Scope
SKILL.md instructs the agent/user to install and run the Membrane CLI, authenticate via browser, create/connect a Textlocal connector, list actions, run actions, and proxy raw API requests through Membrane. It does not instruct reading unrelated files, exporting environment variables, or exfiltrating data to unexpected endpoints.
Install Mechanism
There is no registry install spec, but the instructions ask the user to run `npm install -g @membranehq/cli`. Installing a global npm package is a common but non-trivial action (writes to disk, requires privileges). Verify the npm package publisher and integrity before installing; installing arbitrary npm packages carries moderate risk.
Credentials
The skill declares no required environment variables or credentials and explicitly instructs not to ask users for API keys, instead relying on Membrane-managed connections. This is proportionate to the stated functionality (delegating auth to Membrane).
Persistence & Privilege
The skill is instruction-only, requests no persistent platform privileges (always: false), and does not attempt to modify other skills or system-wide configurations. Autonomous invocation is allowed by default but not exceptional here.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to interact with Textlocal. Before installing or using it, confirm you trust Membrane/@membranehq and the npm package owner; global npm installs modify your system and should be vetted. Expect the login flow to open a browser and for credentials to be managed by Membrane (credentials live on Membrane, not in your local env). If you prefer extra safety, run the CLI in an isolated environment (container or VM), or inspect the @membranehq/cli package on the npm registry/GitHub for source code, publisher, and recent activity before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk978p87j74ghk5ypj9ybqy5er98429yb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.