Psigen Software
v1.0.2PSIGEN Software integration. Manage data, records, and automate workflows. Use when the user wants to interact with PSIGEN Software data.
⭐ 0· 51·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: PSIGEN integration. Requirements and instructions: use Membrane CLI and a Membrane account to connect to PSIGEN and run actions or proxied requests. All required capabilities align with the stated purpose.
Instruction Scope
SKILL.md tells the agent to install and run the Membrane CLI, authenticate via browser, create connections, list actions, run actions, and proxy arbitrary PSIGEN API requests through Membrane. This is expected for a connector but does mean the agent will send request payloads and connector IDs to Membrane (i.e., data flows through Membrane's service).
Install Mechanism
No automated install spec in the registry; the instructions recommend an npm global install (npm install -g @membranehq/cli). This is a standard third-party package install — verify the package name/version and source (npm/membrane repo) before installing in production or privileged environments.
Credentials
The skill requests no local environment variables or credentials and explicitly defers auth to Membrane. That is proportionate, but it implies you are granting Membrane access to PSIGEN data via connections — consider the privacy/trust tradeoff of using a hosted proxy service.
Persistence & Privilege
Skill is instruction-only, no install-time persistence or always:true. It does not request system-wide config changes or elevated privileges.
Assessment
This skill is coherent: it just tells the agent to use the Membrane CLI to connect to PSIGEN. Before installing or using it: 1) Confirm you trust Membrane (getmembrane.com) because connections and API traffic go through their service and they will handle auth/credentials. 2) Verify the npm package @membranehq/cli (name, publisher, repository) and consider installing it in a contained environment rather than globally on a sensitive machine. 3) When creating connections, review what access/permissions the connector requests and check Membrane's privacy/security docs and audit logs for activity. 4) If you cannot or will not route data through a third-party proxy, this skill is not suitable.Like a lobster shell, security has layers — review code before you run it.
latestvk978jnqnetwpzt3rr8ewpeqwhs843efk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.