Demodesk

v1.0.2

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

0· 57·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
Pending
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill claims to integrate with Demodesk and its SKILL.md consistently instructs the agent to use the Membrane CLI to manage Demodesk connections, discover actions, and proxy API requests. Requiring a Membrane account and network access aligns with that purpose. Minor note: the homepage and repository point to Membrane (getmembrane.com / membranedev), which is coherent if Membrane is intended as the integration proxy.
Instruction Scope
The runtime instructions are narrowly scoped: install/run the Membrane CLI, create a connection, list actions, run actions, or proxy requests. They do not instruct reading arbitrary files, unrelated env vars, or modifying other skills. They do instruct interactive browser-based authentication and copying connection IDs from CLI JSON output — expected for this integration.
Install Mechanism
There is no platform install spec; instead SKILL.md tells users to run 'npm install -g @membranehq/cli' or use npx. This is a standard npm install pattern but carries typical npm risks (third-party package execution, need for elevated privileges for global installs). The skill itself does not automatically install anything, but following the instructions will install a public npm package.
Credentials
The skill declares no required env vars or credentials and explicitly advises not to ask users for API keys, instead relying on Membrane to manage auth. This is proportionate to a proxy-based integration. Caveat: the Membrane service will hold and use connection credentials server-side, so trusting that service is required.
Persistence & Privilege
The skill does not request always:true and has no OS restrictions or config path access. It does not ask to modify other skills or system-wide settings. Autonomous invocation is allowed (default) but is not combined with other high-risk features.
Assessment
Before installing or following these instructions, be aware that this skill relies on Membrane (a third-party proxy) to store and use your Demodesk credentials and to forward API requests. Confirm you trust getmembrane.com and the @membranehq/cli npm package (review the npm package page and repository) because installing an npm CLI runs third-party code on your machine. Prefer running 'npx @membranehq/cli@<version>' or review the package contents instead of blindly installing the latest global package. Understand that any requests you proxy through Membrane will be visible to that service; do not use this flow for extremely sensitive data until you've validated Membrane's security/privacy practices. Finally, the skill does not ask for local secrets or extra env vars, but be cautious when running CLI commands that open browsers or require elevated permissions (global npm installs).

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

latestvk9718dvn3mmcjnp72atdj6eqpx843an9

License

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

Comments