Syncro
v1.0.2Syncro integration. Manage Organizations, Tickets, Leads, Emails, Users, Roles. Use when the user wants to interact with Syncro data.
⭐ 0· 92·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
The skill claims to integrate with Syncro and its SKILL.md exclusively instructs use of the Membrane CLI and Membrane's proxy to access Syncro. No unrelated services, credentials, or binaries are requested.
Instruction Scope
Instructions tell the agent to install and use the Membrane CLI, perform login (browser-based or headless), create/connect a Syncro connector, list actions, run actions, and proxy arbitrary API requests through Membrane. These steps stay within the expected scope of integrating with Syncro, but they do give Membrane-wide access to proxy requests on the user's behalf — the user should understand and trust Membrane before proceeding.
Install Mechanism
No install spec in the registry; the SKILL.md recommends installing @membranehq/cli globally with npm (npm install -g). This is a common approach but involves installing third-party software globally — users should review the CLI package and prefer installing in a controlled/sandboxed environment if concerned.
Credentials
The skill declares no environment variables or credentials. It relies on a Membrane account and browser-based auth flows instead of asking for API keys, which is proportional to the described purpose.
Persistence & Privilege
The skill does not request always:true and has no install-time footprint declared. It is instruction-only and does not ask to modify other skills or system-wide agent settings.
Assessment
This skill uses the Membrane CLI to authenticate and proxy requests to Syncro rather than asking for raw API keys — that is expected and coherent. Before installing: (1) verify you trust Membrane (@membranehq/cli) and review the npm package and project homepage; (2) be aware that the login flow stores credentials/tokens managed by Membrane and that proxy requests run through their service; (3) prefer installing the CLI in a sandbox or virtual environment rather than globally if you have security concerns; and (4) review the OAuth/consent screens when connecting Syncro to limit permissions given to the connector.Like a lobster shell, security has layers — review code before you run it.
latestvk978086tzxbf0wy9w43za62hs984314t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.