Outsystems
v1.0.2OutSystems integration. Manage data, records, and automate workflows. Use when the user wants to interact with OutSystems data.
⭐ 0· 88·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
medium confidencePurpose & Capability
The name/description (OutSystems integration) matches the instructions: all runtime steps use the Membrane CLI to discover connectors, create connections, run actions, and proxy API requests to OutSystems. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md confines runtime behavior to installing/using the @membranehq/cli, authenticating via Membrane, listing/connecting actions, and proxying requests to OutSystems. It does not instruct the agent to read unrelated local files or environment variables. The proxy capability can make arbitrary OutSystems API calls (expected for this integration).
Install Mechanism
The skill instructs users to run `npm install -g @membranehq/cli` (and suggests `npx` in places). Installing a global npm package is a normal way to get this CLI but executes code from the npm registry during install — this is a supply-chain risk worth reviewing (check package provenance, review package repo and version, and prefer npx or pinned versions if you want less persistent change).
Credentials
The skill requests no environment variables or local secrets and explicitly instructs not to collect API keys, relying on Membrane to manage auth. It does require a Membrane account and network access, which is proportional for a cloud-proxied integration.
Persistence & Privilege
No special persistence flags (always:true) or system-level config paths are requested. The skill is user-invocable and can be called autonomously by the agent (platform default), which is expected for such a connector.
Assessment
This skill appears consistent with its stated purpose: it uses Membrane as a proxy to access OutSystems and asks you to install the @membranehq CLI. Before installing or using it, do the following: 1) Verify the @membranehq/cli package and source repository on npm/GitHub (review recent release notes and the maintainer identity). 2) Prefer using npx or pinning a specific known-good version instead of wide-open `-g` installs if you want to avoid global changes. 3) Understand that Membrane will hold and refresh OutSystems credentials server-side — only proceed if you trust the Membrane service and its privacy/security posture. 4) Avoid pasting unrelated secrets into commands or prompts. If you want higher assurance, request the skill owner provide a link to the exact npm package release and a commit/tag in the referenced repository so you can inspect the code before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk97e68emvcbx8n3krvzyqfhfbh843nvd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.