Dropcontact

v1.0.0

Dropcontact integration. Manage data, records, and automate workflows. Use when the user wants to interact with Dropcontact data.

0· 55·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Dropcontact integration) matches the instructions: discover and run Membrane-provided Dropcontact actions and proxy Dropcontact API calls. Asking the user to install and use the Membrane CLI is appropriate for this purpose.
Instruction Scope
SKILL.md limits runtime actions to installing/using the Membrane CLI, logging in, creating/listing connections, enumerating actions, running actions, and proxying requests to Dropcontact via Membrane. It does not instruct reading unrelated files, collecting system credentials, or exfiltrating data to arbitrary endpoints.
Install Mechanism
There is no registry install spec (instruction-only), but the guide tells users to run `npm install -g @membranehq/cli`. Installing a global npm CLI is a common but higher-scope operation than a pure instruction-only skill — review and trust @membranehq/cli before installing. No obscure or remote binary downloads are suggested.
Credentials
The skill requests no environment variables or credentials in the registry metadata. It explicitly advises letting Membrane manage credentials and not to ask users for API keys, which is proportionate for a connector-based integration.
Persistence & Privilege
The skill is not marked always:true and does not request system-wide configuration changes. It is an instruction-only skill and does not attempt to persist or escalate privileges.
Assessment
This skill appears coherent: it simply instructs the agent to use the Membrane CLI to connect to Dropcontact and run actions. Before installing or running the CLI, verify you trust the @membranehq/cli package and the Membrane service (review the package repo and privacy/security docs), because using the proxy means requests and authentication are handled by Membrane's servers. Installing the CLI globally requires npm privileges — avoid running commands you don't trust. If you handle sensitive PII, confirm Membrane's data-handling policies and consider reviewing the CLI source code before use.

Like a lobster shell, security has layers — review code before you run it.

latestvk97a3mw5xjhbfj49y72gmn40ts844wzp

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments