Screendesk
v1.0.2Screendesk integration. Manage Organizations. Use when the user wants to interact with Screendesk data.
⭐ 0· 94·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 (Screendesk integration) match the runtime instructions: all actions are performed via the Membrane CLI and Membrane account. Requesting use of a connector/proxy (Membrane) is appropriate for this integration.
Instruction Scope
SKILL.md instructs the agent to install and use the Membrane CLI, run connector discovery, create connections, list/run actions, and optionally proxy raw API calls via Membrane. It does not ask the agent to read unrelated files, secrets, or system configuration.
Install Mechanism
The skill is instruction-only (no install spec) but tells the user to run `npm install -g @membranehq/cli` (or use npx). Installing a global npm CLI is expected for this workflow but carries the usual risks of running third‑party npm packages (postinstall scripts etc.).
Credentials
No environment variables, credentials, or config paths are requested by the skill. Authentication is delegated to Membrane via browser login, which is consistent with the documented workflow.
Persistence & Privilege
Skill is user-invocable and not set to always:true. It does not request persistent system-wide privileges or modify other skills' configurations in its instructions.
Scan Findings in Context
[no-findings] expected: The static scanner had nothing to analyze because this is an instruction-only skill (SKILL.md). No code files or regex matches were present.
Assessment
This skill appears coherent and uses Membrane as an integration proxy for Screendesk. Before installing/using it: 1) Verify you trust Membrane/@membranehq/cli (check the npm package page, GitHub repo, and package maintainers). 2) Prefer using `npx @membranehq/cli` if you want to avoid a global install. 3) During `membrane login` review what permissions and scopes you grant in the browser. 4) Remember that once a Membrane connection exists, commands like `membrane request` can read/modify Screendesk data — only connect accounts you intend to expose. 5) If you need maximum assurance, review the Membrane CLI source and its npm package metadata before running a global install.Like a lobster shell, security has layers — review code before you run it.
latestvk9745dg35qv31hdrmr7g47pfxd843mrt
License
MIT-0
Free to use, modify, and redistribute. No attribution required.