Performyard
v1.0.3PerformYard integration. Manage data, records, and automate workflows. Use when the user wants to interact with PerformYard data.
⭐ 0· 83·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 (PerformYard integration) matches the instructions: all actions use the Membrane CLI and Membrane's proxy to interact with PerformYard. No unrelated services, env vars, or binaries are requested.
Instruction Scope
SKILL.md stays on topic: it describes installing/using the Membrane CLI, logging in via browser, listing/creating connections, running actions, and proxying API requests. It does not instruct reading arbitrary system files or exfiltrating data outside the Membrane/PerformYard flow.
Install Mechanism
There is no install spec, but the instructions recommend installing @membranehq/cli via npm -g (or using npx in one example). Installing global npm packages runs third-party code—this is a normal requirement for a CLI but carries standard supply-chain risk and requires user trust in the package and registry.
Credentials
The skill declares no required env vars or credentials and instead relies on Membrane's browser-based login and server-side auth. That is proportionate for a connector-oriented integration. Users should still confirm what access the Membrane connection grants to their PerformYard account.
Persistence & Privilege
always is false and the skill does not request persistent system-wide changes or access to other skills' configurations. Autonomous invocation is allowed (platform default) but not combined with elevated privileges.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to connect to PerformYard and does not ask for unrelated secrets. Before installing, verify you trust @membranehq/cli and getmembrane.com (review the npm package page and Membrane's privacy/terms). Prefer using the npx example or pinning a specific CLI version instead of a global -g install if you want to reduce system-wide changes. When creating a connection, check the permission scope and data access Membrane will have in your PerformYard tenant. Finally, be aware the agent can call the skill autonomously (platform default); if you don't want that, restrict agent invocation in your settings.Like a lobster shell, security has layers — review code before you run it.
latestvk97c1p2pw0y2mxcjgqxr3xr4x58436ct
License
MIT-0
Free to use, modify, and redistribute. No attribution required.