Getaccept
v1.0.2GetAccept integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with GetAccept data.
⭐ 0· 87·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 (GetAccept integration) align with the runtime instructions: all actions are routed through the Membrane CLI and Membrane connections to GetAccept. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md confines runtime behavior to installing/using the Membrane CLI, creating/listing Membrane connections, running pre-built actions, and proxying requests to the GetAccept API via Membrane. It does not instruct reading arbitrary files, harvesting unrelated environment variables, or transmitting data to unexpected external endpoints beyond Membrane/GetAccept.
Install Mechanism
The skill recommends installing the @membranehq/cli package globally via npm. This is a plausible requirement, but global npm installs execute package scripts and write to the system; installing any third-party global package carries moderate risk. Verify package provenance (publisher, npm/GitHub repo) before installing or prefer a constrained environment (container/VM/user-local install).
Credentials
No environment variables, keys, or config paths are requested by the skill. The instructions explicitly say to let Membrane handle credentials and not to ask users for API keys, which is proportionate for this integration.
Persistence & Privilege
Skill does not request always:true, does not modify other skills, and has no install spec writing files itself (instructions ask the user to install a CLI). Normal autonomous invocation is allowed but not combined with elevated privileges.
Assessment
This skill appears coherent and only requires the Membrane CLI and a Membrane account. Before installing: (1) verify the CLI package @membranehq/cli on npm/GitHub and confirm the publisher is legitimate; (2) prefer installing the CLI in a sandbox (container, VM, or user-local) if you are cautious about global npm installs; (3) understand that you will authenticate via browser and grant Membrane access to your GetAccept data — ensure you trust Membrane as the proxy for API calls; (4) review the Membrane connection permissions and connector IDs before authorizing; (5) if you need higher assurance, inspect the Membrane CLI source or use a temporary account to test.Like a lobster shell, security has layers — review code before you run it.
latestvk97bb01rg8qts5hp3j79rvm3cs843b45
License
MIT-0
Free to use, modify, and redistribute. No attribution required.