Verdict As A Service
v1.0.2Verdict as a Service integration. Manage data, records, and automate workflows. Use when the user wants to interact with Verdict as a Service data.
⭐ 0· 77·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
medium confidencePurpose & Capability
The name/description claim integration with Verdict as a Service and the SKILL.md consistently instructs the agent to use the Membrane CLI to discover/connect/run actions against that service — this is coherent. Minor inconsistency: the 'Official docs' link points to docs.beyondidentity.com (a different vendor) which looks like a copy/paste or attribution error and should be verified.
Instruction Scope
Runtime instructions are narrowly scoped to installing and using the Membrane CLI (login, search/connect, action run, proxy requests). The SKILL.md does not instruct reading unrelated files or environment variables and tells the user not to share API keys, so scope is appropriate.
Install Mechanism
No packaged install spec in the skill bundle (instruction-only). The SKILL.md asks the user to run `npm install -g @membranehq/cli` — installing a global npm package executes third-party code and is a moderate-risk action that is nonetheless expected for a CLI-based integration. Recommend verifying the npm package and source before installing globally.
Credentials
The skill declares no required environment variables or credentials and explicitly recommends using Membrane connections rather than asking for API keys. Requested access (Membrane account and network) is proportionate to the described functionality.
Persistence & Privilege
The skill is user-invocable, not always-enabled, and does not request system-wide config changes. There are no indicators it would persistently modify other skills or system settings.
Assessment
This skill appears to be a thin instruction wrapper telling you to use the Membrane CLI to access Verdict as a Service. Before installing or running it: (1) verify the Membrane project and npm package (@membranehq/cli) on npm and the referenced GitHub repo to ensure they are legitimate; (2) consider installing the CLI in a user or container environment rather than globally if you want to limit risk; (3) be cautious with the browser-based auth flow (do not paste secrets into untrusted prompts); (4) note the odd 'Official docs' link to beyondidentity.com — confirm the correct vendor documentation and that the connector you use is indeed the Verdict as a Service connector you expect.Like a lobster shell, security has layers — review code before you run it.
latestvk973f2fqy2sfw4g6270y1ty9dn843et9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.