ClawHub

Testrail

v1.0.2

TestRail integration. Manage data, records, and automate workflows. Use when the user wants to interact with TestRail data.

⭐ 0· 58·1 current·1 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill declares TestRail integration and all runtime instructions are about using the Membrane CLI to discover connectors, create a connection, run actions, or proxy TestRail API calls — which matches the stated purpose.
✓
Instruction Scope
SKILL.md only instructs the agent/operator to install and use the Membrane CLI, authenticate via browser, create/list connections, list/run actions, and proxy requests to TestRail. It does not instruct reading unrelated files or exfiltrating secrets. It explicitly advises against asking users for API keys.
ℹ
Install Mechanism
There is no packaged install spec in the registry, but the instructions ask the operator to install the Membrane CLI via npm (global install) or use npx. Global npm installs are common for CLIs but have standard risks (e.g., elevated PATH changes). The skill does not supply or download arbitrary archives or external URLs.
✓
Credentials
The skill declares no required environment variables or credentials; authentication is delegated to Membrane's browser-based login/connector flow, which is appropriate for this integration.
✓
Persistence & Privilege
The skill is instruction-only and does not request permanent presence (always:false) nor ask to modify other skills or system-wide settings. Autonomous invocation is allowed by platform default but is not combined with broad access in this skill.
Assessment
This skill is coherent: it uses the Membrane CLI to connect to TestRail and does not ask for unrelated credentials. Before installing/using it, verify you trust Membrane (@membranehq) and the upstream CLI (npm package @membranehq/cli). Be aware you will perform a browser-based login that grants Membrane access to TestRail on your behalf (so check what scopes/permissions the connector requests). Installing a global npm CLI changes your environment PATH — if you prefer not to install globally, use npx as shown. Do not paste your TestRail API keys or other secrets into chat; use the connector flow so Membrane can handle auth securely. If you need higher assurance, review the Membrane CLI source on the referenced repository and the connector configuration before authorizing.

Like a lobster shell, security has layers — review code before you run it.

latestvk9734yb0h6sj58z9x82eat3yp5843p4n

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments