Tiledesk
v1.0.0Tiledesk integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tiledesk data.
⭐ 0· 54·0 current·0 all-time
byMembrane Dev@membranedev
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 Tiledesk and its runtime instructions exclusively describe using the Membrane CLI to discover connectors, create connections, run actions, and proxy requests to Tiledesk — these requirements are consistent with the stated purpose.
Instruction Scope
SKILL.md confines actions to installing and using the Membrane CLI, logging in via browser, listing connections/actions, running actions, and proxying requests. It does not instruct reading unrelated local files, accessing unrelated env vars, or exfiltrating data outside the Membrane/Tiledesk flow.
Install Mechanism
The guide asks the user to install @membranehq/cli via npm (-g). Using an npm package is expected for a CLI, but global npm installs carry normal supply-chain risk — verify the package and publisher (npm listing, GitHub repo) before installing, especially on production machines.
Credentials
No environment variables, local config paths, or additional credentials are requested by the skill; it explicitly instructs not to ask users for API keys and relies on Membrane to manage auth, which is proportionate to the task.
Persistence & Privilege
The skill is instruction-only, has no install spec that writes files, and does not request always:true. Autonomous invocation is allowed (platform default) but not combined with unusual privileges or credential access.
Assessment
This skill is coherent: it expects you to install and use the Membrane CLI and a Membrane account to manage Tiledesk connections and requests. Before installing/using it: 1) verify the @membranehq/cli package and publisher on npm and the referenced GitHub repository; 2) understand that using the skill will route API calls and data through Membrane's service (so review their privacy/security docs and your organization's policy); 3) avoid running global npm installs on sensitive production hosts without review; and 4) if you need to operate in a headless or highly restricted environment, confirm the login flow and token storage details from Membrane first.Like a lobster shell, security has layers — review code before you run it.
latestvk97dzbsaax0xa6maz6qydrptfn8462rw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.