Chatra
v1.0.2Chatra integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chatra data.
⭐ 0· 99·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
OpenClaw
Benign
medium confidencePurpose & Capability
The skill's described purpose (Chatra integration) aligns with the provided instructions (use Membrane CLI to connect, list actions, run actions, or proxy Chatra API calls). Minor inconsistency: the skill metadata declares no required binaries, but the runtime instructions expect npm (and Node) to be available to install the @membranehq/cli and also expect the membrane CLI to be runnable.
Instruction Scope
Instructions stay within the stated purpose (creating connections, running actions, proxying API calls). Important operational detail: proxying sends requests through Membrane's servers and Membrane manages the Chatra authentication lifecycle—so user data and API calls will transit/ be handled by Membrane. The instructions do not ask the agent to read unrelated local files or environment variables.
Install Mechanism
No automated install is bundled with the skill (lower risk). The SKILL.md instructs a global npm install of @membranehq/cli, which is a public npm package (traceable) but is an external dependency the user must run. Global npm installs may require elevated privileges and modify the host environment.
Credentials
The skill does not request environment variables or local credentials. It relies on a Membrane account and network access, which is appropriate for a connector that delegates auth to a third-party service. Note: trusting Membrane with credentials and proxied data is required.
Persistence & Privilege
The skill does not request persistent/always-on privileges and is user-invocable only. There is no install script included in the skill bundle that would persist or modify other skill configurations.
Assessment
Before installing or following the SKILL.md: (1) Verify and trust the Membrane project (@membranehq) on npm and GitHub (check package page, repo, and reviews). (2) Be aware you'll need npm/Node to run a global install and that global installs can require admin rights. (3) Understand that API calls and user data will be proxied through Membrane (they will see the data and hold Chatra credentials); review Membrane's privacy/security docs. (4) The skill metadata omits 'npm' as a required binary even though the instructions need it—ensure your environment can run the CLI before use. (5) If you need stricter data controls, consider using direct Chatra API keys or reviewing Membrane's tenancy/separation model before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97167en2j3czbafhnhg4tpc1n84265r
License
MIT-0
Free to use, modify, and redistribute. No attribution required.