Practitest
v1.0.2PractiTest integration. Manage Projects. Use when the user wants to interact with PractiTest data.
⭐ 0· 96·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
high confidencePurpose & Capability
The name/description (PractiTest integration) match the instructions, which only show how to install and use the Membrane CLI to connect to PractiTest, discover actions, run them, or proxy API requests. Nothing requested is unrelated to integrating with PractiTest via Membrane.
Instruction Scope
SKILL.md only instructs installing/running the Membrane CLI, logging in, creating/listing connections, running actions, and proxying requests. It does not instruct reading local files, environment variables, or system configuration outside of normal CLI usage. Note: proxying requests sends API calls through Membrane's servers, so PractiTest data will transit / be handled by the Membrane service.
Install Mechanism
There is no install spec in the skill bundle itself, but the guide tells users to install @membranehq/cli via npm -g (or use npx). Installing a public npm CLI is a common pattern but has moderate risk compared to no install; verify the package and prefer npx or pinned versions if you want to avoid a global install.
Credentials
The skill declares no required environment variables or credentials. It delegates auth to Membrane, so no local API keys are requested. The tradeoff is that you must trust Membrane to store/handle PractiTest credentials and proxied data.
Persistence & Privilege
always is false and the skill does not request persistent system-wide privileges or modify other skills. Autonomous model invocation is allowed by default (normal) and appropriate for this integration.
Assessment
This skill appears coherent and limited in scope, but before installing: (1) verify the @membranehq/cli package and its publisher (use npx or pin a version if you prefer not to install globally); (2) understand that authentication and API calls are handled by Membrane — PractiTest data will transit or be stored by that third-party service, so confirm that is acceptable under your security and privacy policies; (3) be prepared for the CLI to open a browser for login or print an auth URL for headless use; and (4) if you need stricter control over credentials or auditing, consider using your own tooling or a direct PractiTest integration instead.Like a lobster shell, security has layers — review code before you run it.
latestvk97bec9x8qf9jcvqreqpctxxpx843ex6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.