Snapdocs
v1.0.2Snapdocs integration. Manage Organizations, Users, Roles. Use when the user wants to interact with Snapdocs data.
⭐ 0· 104·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/description match the instructions: the SKILL.md describes interacting with Snapdocs via the Membrane CLI and the commands shown (connect, action run, request proxy) are consistent with that purpose. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions are narrowly scoped to installing and using the Membrane CLI, creating a connection, listing actions, running actions, and proxying requests to the Snapdocs API. The skill does not instruct reading unrelated files, env vars, or exfiltrating data outside the Membrane/Snapdocs flow.
Install Mechanism
This is an instruction-only skill, but it tells users to run `npm install -g @membranehq/cli` and use `npx @membranehq/cli@latest`. Installing/running code from npm executes third-party code on the host — a moderate-risk action that is reasonable for a CLI integration but worth verifying (package provenance, publisher, audit, and use of `@latest`).
Credentials
The skill requests no environment variables or local credential files. Authentication is delegated to Membrane (browser-based login and server-side credential management), which is proportionate to the stated purpose. The user must be comfortable granting Membrane account access to manage Snapdocs credentials.
Persistence & Privilege
The skill does not request always:true and has no install-time persistence in the manifest. Any persistence comes from installing the Membrane CLI, which is typical for this integration and does not modify other skills or system-wide agent settings per the provided instructions.
Assessment
This skill is coherent: it uses the Membrane CLI to talk to Snapdocs and asks for no unrelated secrets. Before installing, verify the @membranehq/cli package (publisher, npm page, repository) since the SKILL.md asks you to globally install and/or run the package via npx — that runs third-party code on your machine. Understand that authentication is handled by Membrane: creating a connection grants Membrane the ability to access Snapdocs on your behalf, so review their access model and privacy/security docs. If you prefer less host impact, consider running the CLI in an isolated environment (container/VM) or reviewing the package source before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97bjxtscjqx9s2bq91kzje0998429s3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.