Harness
v1.0.0Harness integration. Manage data, records, and automate workflows. Use when the user wants to interact with Harness data.
⭐ 0· 61·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 and description say 'Harness integration' and all runtime instructions use Membrane to connect to Harness; requested capabilities (network access, Membrane account) match the stated purpose. No unrelated credentials, binaries, or config paths are demanded.
Instruction Scope
SKILL.md confines actions to installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to Harness via Membrane. It does not instruct reading unrelated files or environment variables, nor does it direct data to unexpected external endpoints beyond Membrane/Harness.
Install Mechanism
There is no registry install spec; the README instructs users to install @membranehq/cli via npm (npm install -g). This is a common approach but carries the usual npm install risks (code runs at install time). The instruction is expected for this integration but users should verify the package/source before installing.
Credentials
The skill declares no required env vars and explicitly advises not to ask users for API keys, instead using Membrane-managed auth. Requiring a Membrane account and browser-based login is proportionate to the described functionality.
Persistence & Privilege
Skill is instruction-only, does not request persistent presence or special privileges (always is false). It does not modify other skills or system-wide settings.
Assessment
This skill is coherent: it tells the agent to use the Membrane CLI to access Harness and requires a Membrane account. Before installing or using it, verify you trust Membrane/@membranehq and their npm package (npm install -g runs third-party code on your machine). Confirm the browser-based login/connector workflow with your security policies (it will grant Membrane access to Harness data on your behalf). If you need to limit exposure, review Membrane's docs and permissions for connectors and consider using a dedicated, least-privilege account for the integration.Like a lobster shell, security has layers — review code before you run it.
latestvk97cag57t689v175vq3k7c57b58485gb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.