Everlaw
v1.0.2Everlaw integration. Manage data, records, and automate workflows. Use when the user wants to interact with Everlaw data.
⭐ 0· 94·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 (Everlaw integration) align with the instructions (use the Membrane CLI to create/connect Everlaw connectors). The only minor inconsistency is that the registry metadata lists no compatibility or network requirements while SKILL.md explicitly says it requires network access and a Membrane account — this is an informational mismatch but not malicious.
Instruction Scope
The SKILL.md only instructs installing and using the Membrane CLI, running login/connect/action list commands, and parsing JSON outputs. It does not ask the agent to read unrelated files, system credentials, or exfiltrate data to unexpected endpoints. It does instruct interactive browser-based auth flows (membrane login), which is expected for OAuth-style connectors.
Install Mechanism
There is no formal install spec in the registry, but SKILL.md recommends installing @membranehq/cli via npm (npm install -g @membranehq/cli). Installing an npm global package is a common and expected mechanism for this type of integration, but it carries the usual moderate risk of running third‑party code from the npm registry — verify the package and author before installing.
Credentials
The skill requests no environment variables or local config paths in the registry. Authentication is delegated to the Membrane CLI/browser flow, which is proportionate to the stated purpose of connecting to Everlaw. No unrelated credentials are requested.
Persistence & Privilege
The skill is instruction-only, has always:false, and does not request persistent system-wide privileges or modify other skills. Autonomous invocation is allowed by platform default but not escalated by this skill's metadata.
Assessment
This skill appears coherent: it tells you to install the Membrane CLI and use it to create/connect an Everlaw connector. Before installing/using it, verify the @membranehq/cli package and its GitHub repo (author, recent activity, and reviews), because npm packages execute code on install. Understand that Membrane (the CLI/connector) will obtain access to Everlaw data via the browser auth flow — confirm the permissions/scopes requested and use a least‑privilege account or a test tenant if possible. Do not paste Everlaw credentials into third-party tools; follow the browser OAuth flow. If you cannot verify the Membrane package or prefer not to install global npm packages, do not install the CLI and consider interacting with Everlaw through your own vetted tooling or official SDKs/APIs.Like a lobster shell, security has layers — review code before you run it.
latestvk970ws0ypbrq75v6z0ba8b5tmd842nz5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.