Testmo
v1.0.0Testmo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Testmo data.
⭐ 0· 53·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
Name / description (Testmo integration) align with the instructions: all actions are performed via the Membrane CLI and Membrane connections to Testmo. No unrelated credentials, binaries, or paths are requested.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, creating connections, listing/running actions, and proxying requests to Testmo. This is coherent, but proxying allows arbitrary HTTP requests to be sent through Membrane — user data and request bodies will transit Membrane's infrastructure, so treat sensitive payloads accordingly.
Install Mechanism
There is no built-in install spec (instruction-only). The doc instructs users to install @membranehq/cli via npm (global install or npx). This is a standard public npm package approach; users should verify the package identity and be aware global npm installs modify the host environment.
Credentials
No environment variables, credentials, or config paths are requested by the skill. The SKILL.md explicitly instructs not to ask for API keys and to use Membrane-managed connections instead, which is proportionate to the stated purpose.
Persistence & Privilege
The skill is not always-enabled and does not request special system persistence or modify other skills. It relies on user-invoked CLI commands and browser-based auth flows; autonomous invocation is permitted by default but not granted extra privileges.
Assessment
This skill is an instructions-only integration that uses the Membrane CLI to connect to Testmo. Before installing or using it: (1) verify you trust the @membranehq npm package (check package page, publisher, and repo), (2) understand that requests and payloads will transit Membrane's servers (review Membrane's privacy/security docs if sending sensitive data), (3) prefer using npx or a scoped/local install if you want to avoid a global npm install, and (4) in headless or automated environments, confirm the login flow and tokens are acceptable for your security posture. The skill itself does not ask for unrelated secrets or system access.Like a lobster shell, security has layers — review code before you run it.
latestvk978d62hzqk4pr4c20hasq8pg9844np5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.