Apaya
v1.0.0Apaya integration. Manage data, records, and automate workflows. Use when the user wants to interact with Apaya 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
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, and instructions all describe using the Membrane CLI to interact with Apaya. Required capabilities (network and a Membrane account) are appropriate for that purpose and nothing unrelated (e.g., AWS keys) is requested.
Instruction Scope
SKILL.md instructs the agent to use the Membrane CLI (search, connect, action list/run, request). It does not ask the agent to read arbitrary files, environment variables, or other system state beyond what is needed to run the CLI and authenticate via Membrane.
Install Mechanism
There is no automated install spec in the skill package (lowest-risk), but the documentation tells the user/agent to install @membranehq/cli via npm -g or npx. This is expected for a CLI-based integration but means the agent/user will bring third-party code into their environment — verify you trust the Membrane CLI before installing globally.
Credentials
The skill declares no required env vars or credentials. The instructions rely on Membrane to manage credentials (which is consistent with the written guidance). There are no unrelated credential requests.
Persistence & Privilege
Skill does not request always:true and does not attempt to modify system or other skills' configuration. It is user-invocable and allows autonomous invocation (platform default), which is expected for a skill of this type.
Assessment
This skill is a set of instructions for using the Membrane CLI to manage Apaya data — it doesn't itself include code or ask for secrets. Before installing or running the CLI: 1) confirm you trust Membrane/@membranehq and the homepage/repository; 2) be aware installing @membranehq/cli globally will add a third-party binary to your system; 3) the CLI will open a browser for auth and can proxy requests to the Apaya API, so grant it only the accounts you intend; 4) review any actions returned by membrane action list before running them (they may accept arbitrary inputs); and 5) if you prefer not to install global packages, use npx or run in a controlled environment. If you want extra assurance, inspect the Membrane CLI source code or run it in an isolated container/environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk97a273j9an9bnnmg2xb7bk2h584chkt
License
MIT-0
Free to use, modify, and redistribute. No attribution required.