Seam
v1.0.0Seam integration. Manage data, records, and automate workflows. Use when the user wants to interact with Seam data.
⭐ 0· 30·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
The skill claims to integrate with Seam and the SKILL.md exclusively instructs use of the Membrane CLI and Seam APIs via Membrane. Required tools and actions (membrane CLI, browser-based auth, proxying requests to Seam) align with the described purpose; no unrelated credentials, binaries, or system paths are requested.
Instruction Scope
Instructions stay within the Seam integration scope (discover actions, run actions, or proxy requests). They require network access and browser-based login. Notably, the skill relies on Membrane's proxy/auth — meaning API calls and credentials are managed by Membrane's service and requests will flow through that service. This is expected for this integration but is a privacy/trust consideration for users.
Install Mechanism
There is no registry install spec; the SKILL.md tells users to run `npm install -g @membranehq/cli`. Installing a global npm package is a typical but elevated action (executes third-party code on the host). The package is published under a scoped name on the public registry (moderate risk). Users should verify the package identity and trustworthiness before installing globally.
Credentials
The skill does not request environment variables, keys, or config paths. Authentication is handled via Membrane's login flow; the SKILL.md explicitly instructs not to collect API keys locally. The level of credential access is proportionate to the stated function, but remember Membrane will hold/manage delegated credentials on behalf of the user.
Persistence & Privilege
The skill is instruction-only, does not request 'always' presence, and does not modify other skills or system-wide configs. It requires the Membrane CLI and a user login but does not demand persistent agent privileges beyond normal runtime use.
Assessment
This skill appears to do what it says: it integrates with Seam via the Membrane CLI. Before using it: 1) Verify you trust Membrane (https://getmembrane.com) because requests and delegated credentials will be handled by their service. 2) Inspect the npm package (@membranehq/cli) on the npm registry/GitHub to confirm authorship and recent activity before running a global install. 3) Prefer running the CLI in an isolated environment or container if you are cautious about installing global packages. 4) When creating a connection to Seam, review the permissions requested and revoke access if no longer needed. If you need further assurance, ask the skill author for a reproducible, non-global install option (local install or Docker) and a link to the exact CLI package repository and release used.Like a lobster shell, security has layers — review code before you run it.
latestvk9728sdf8vjdd3jbdnav46xay5847dha
License
MIT-0
Free to use, modify, and redistribute. No attribution required.