Salesblink
v1.0.2SalesBlink integration. Manage Organizations, Pipelines, Projects, Users, Filters. Use when the user wants to interact with SalesBlink data.
⭐ 0· 97·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
Name/description (SalesBlink integration) align with the instructions: all actions are performed via the Membrane CLI and the skill is explicitly about managing SalesBlink data. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md limits runtime behavior to installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to SalesBlink through Membrane. It does not instruct reading local files, harvesting unrelated env vars, or sending data to unexpected endpoints.
Install Mechanism
There is no install spec in the registry (instruction-only), but the document recommends installing the @membranehq/cli globally via npm. Installing a global npm package is common for CLIs but does carry the usual supply-chain/trust considerations; the recommendation itself is proportionate to the described functionality.
Credentials
The skill declares no required env vars or credentials and explicitly instructs to let Membrane handle auth rather than asking for API keys. That is appropriate given the Membrane-based design. Note: using Membrane implies you will authorize Membrane to access SalesBlink on your behalf (OAuth-like flow).
Persistence & Privilege
The skill is not always-enabled and does not request persistent system privileges or modify other skills. Autonomous invocation is allowed by default (normal) but this skill does not add extra persistent privileges.
Assessment
This skill is coherent: it uses the Membrane CLI to interact with SalesBlink and does not ask for unrelated credentials. Before installing, confirm you trust the @membranehq/cli package and its publisher (check the npm page and repository at https://github.com/membranedev/application-skills or the official Membrane site). Installing a global npm CLI is normal but carries standard supply-chain risk—prefer verifying package authenticity (publisher, README, recent activity, checksum) before npm install -g. Also be aware that authorizing a connection will give Membrane access to your SalesBlink data, so review the OAuth/consent screens and Membrane's privacy/security documentation. If you plan to use headless or CI environments, follow Membrane's documented headless flow and avoid pasting creds into untrusted consoles.Like a lobster shell, security has layers — review code before you run it.
latestvk975j17q8fdajwrt3kxyt09hdd843geg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.