Humanity

v1.0.0

Humanity integration. Manage data, records, and automate workflows. Use when the user wants to interact with Humanity data.

0· 56·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Humanity integration) match the instructions: all actions are performed via the Membrane CLI which proxies requests to Humanity. Nothing requested (no extra env vars, no unrelated binaries) contradicts the stated purpose.
Instruction Scope
SKILL.md confines runtime actions to installing/using the Membrane CLI, logging in, creating connections, listing/running actions, and proxying Humanity API calls. It does not instruct reading unrelated local files or exfiltrating data. Note: the proxy command can reach arbitrary Humanity endpoints (expected for an API integration).
Install Mechanism
The registry contains no formal install spec (instruction-only), but the instructions ask the user to run `npm install -g @membranehq/cli` (or npx). Installing a global npm package executes third-party code on the machine — this is expected here but is an elevated action the user must trust.
Credentials
The skill declares no required environment variables or secrets. Authentication is delegated to Membrane via an interactive login flow, which is proportionate to the described integration.
Persistence & Privilege
The skill is instruction-only and not force-included (always:false). It does not request persistent system privileges or modify other skills. Agent autonomy is platform-default and not uniquely elevated here.
Assessment
This skill appears coherent for connecting to Humanity via Membrane, but review and trust the Membrane CLI before installing: global npm installs run third-party code — prefer using the suggested npx invocation or run the CLI in an isolated environment (container/VM) if you are cautious. Check what Humanity permissions the Membrane connection requests, review the @membranehq/cli package on npm and the linked GitHub repo, and only connect accounts you consent to share with Membrane (it will be able to read/write Humanity data and proxy arbitrary API endpoints). If you manage sensitive systems, avoid a global install or test in a sandbox first.

Like a lobster shell, security has layers — review code before you run it.

latestvk970tgq1n7f0sypzjw16b45n0984cqye

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments