Textgain
v1.0.2Textgain integration. Manage data, records, and automate workflows. Use when the user wants to interact with Textgain data.
⭐ 0· 67·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 claims to integrate with Textgain and all runtime instructions use the Membrane CLI and Membrane connections to access Textgain — this is coherent. However, the registry metadata lists no required binaries while the SKILL.md explicitly instructs installing @membranehq/cli (membrane). The dependency is reasonable for the stated purpose but the metadata omission is a mismatch.
Instruction Scope
SKILL.md instructs only on installing and using the Membrane CLI, creating connections, listing and running actions, and proxying requests to Textgain. It does not ask to read unrelated local files, harvest environment variables, or transmit data to unexpected endpoints. It explicitly recommends letting Membrane handle credentials rather than asking the user for API keys.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the runtime instructions tell the user/agent to run `npm install -g @membranehq/cli` (or use npx). Installing a global npm CLI is a normal but persistent action; the package is from the npm registry (not a third-party URL). The lack of an install spec in metadata is an inconsistency to be aware of.
Credentials
The skill declares no required environment variables or credentials and the instructions rely on Membrane-managed connections (browser-based auth). There are no requests for unrelated secrets or broad environment access. Giving Membrane access to your Textgain account is expected for this integration and is the main credential surface.
Persistence & Privilege
The skill does not request always: true and does not attempt to modify other skills or system-wide agent settings. The main persistence impact is installing a global CLI (if chosen), which modifies the host environment but is a user action rather than an automatic change by the skill metadata.
Assessment
Before installing/use: 1) Understand that this skill delegates Textgain access to the Membrane platform — Membrane will handle auth and will be able to proxy requests to Textgain and see request/response data. Only proceed if you trust Membrane and the account you sign into. 2) The SKILL.md asks you to install a global npm CLI (@membranehq/cli). If you prefer not to change global system state, use `npx @membranehq/cli` or run it in a controlled environment. 3) Verify the @membranehq/cli package and its homepage/repository (audit the npm package, check GitHub repo and maintainers) before installing. 4) Note the metadata omission: the registry did not declare the Membrane CLI as a required binary even though the instructions need it — treat that as a minor red flag in packaging quality. 5) If you need higher assurance, request the skill author to include an install spec in metadata or provide an explicit list of required binaries and link to the exact npm package/release used.Like a lobster shell, security has layers — review code before you run it.
latestvk978p42hp08fcxpvhbbqw1a82n843b8z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.