Progress Sitefinity
v1.0.2Progress Sitefinity integration. Manage data, records, and automate workflows. Use when the user wants to interact with Progress Sitefinity 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
Name/description match the instructions: the SKILL.md documents using the Membrane CLI to connect to a Progress Sitefinity connector, list actions, run actions, and proxy arbitrary Sitefinity API calls. All required pieces are relevant to the stated purpose.
Instruction Scope
Instructions are scoped to installing/using the Membrane CLI, creating a connection, listing/running actions, and proxying API requests. There are no instructions to read unrelated local files, harvest environment variables, or exfiltrate data beyond the Membrane proxy flow.
Install Mechanism
The skill recommends installing @membranehq/cli via npm (global install) and sometimes using npx. This is a standard distribution channel (npm) but carries the usual considerations: global npm installs require elevated permissions and you should trust the package and publisher. No arbitrary URL downloads or archive extraction are used.
Credentials
No environment variables or local credentials are requested, which is proportional. However, the instructions route API calls and authentication through Membrane (getmembrane.com), so Sitefinity data and request payloads will be proxied by a third-party service — review that service's data handling and access model before use.
Persistence & Privilege
Skill is instruction-only, always:false, and does not request persistent system privileges or modify other skills/config. It relies on the Membrane CLI for runtime, so it does not attempt to gain unusual presence on the agent.
Assessment
This skill is coherent with its description, but before installing: (1) confirm you trust Membrane (getmembrane.com) and review its privacy/security policy because Sitefinity requests and content will be proxied through their service; (2) prefer using npx to avoid a global npm install or run the CLI in a contained environment; (3) authenticate using a least-privilege Sitefinity account when creating the connection; (4) verify the @membranehq/cli npm package and publisher reputation (GitHub repo and npm page) if you plan to install it globally.Like a lobster shell, security has layers — review code before you run it.
latestvk9714e7bz0308ygda0cyexnrnx842s1y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.