Mews
v1.0.0Mews integration. Manage Customers, Spaces, Products, Rates, Reservations, Payments and more. Use when the user wants to interact with Mews data.
⭐ 0· 180·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 name and description (Mews integration) match the SKILL.md: it documents using Membrane to connect to Mews, discover actions, run actions, and proxy API requests. Required resources (a Membrane account and network) are appropriate for this purpose.
Instruction Scope
Instructions stay within the integration scope (install Membrane CLI, login, create/connect, list actions, run actions, and proxy requests). Note that the proxy feature lets you call arbitrary Mews API endpoints through Membrane — this is expected for an integration but means the skill can be used to retrieve or modify any data the connected account permits.
Install Mechanism
There is no registry install spec; the SKILL.md tells users to npm install -g @membranehq/cli. Using a public npm package is standard for a CLI, but global npm installs require appropriate privileges and trust in the @membranehq package and publisher.
Credentials
The skill declares no required environment variables or secrets and explicitly relies on Membrane to manage credentials server-side. That is proportionate to the described behavior. Be aware that Membrane will hold and use the Mews credentials for proxying requests.
Persistence & Privilege
The skill is instruction-only with no install payload and no 'always' privilege. It does not request persistent presence or modify other skills/config; autonomy settings are default.
Assessment
This skill appears to be what it says: a Mews integration that operates via the Membrane CLI. Before installing: (1) verify you trust Membrane/@membranehq (check npm package, homepage, privacy/TOS), since you'll install their CLI and authenticate through their service; (2) be prepared for the CLI to open a browser for login or use a headless code flow; (3) understand that Membrane will hold and use your Mews credentials and can proxy arbitrary API calls — grant the connection only the minimum permissions needed; (4) prefer running the CLI in a controlled environment (not an untrusted shared machine); and (5) if you need stronger assurance, review Membrane's docs or source code and restrict the connector permissions in Mews where possible.Like a lobster shell, security has layers — review code before you run it.
latestvk977aaerh29zk0mf273n1emmcn82vpza
License
MIT-0
Free to use, modify, and redistribute. No attribution required.