Agenty
v1.0.2Agenty integration. Manage data, records, and automate workflows. Use when the user wants to interact with Agenty data.
⭐ 0· 101·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
Name/description (Agenty integration) align with the instructions: the SKILL.md describes using Membrane to manage Agenty resources and lists relevant actions. The required capabilities (network access, a Membrane account, Membrane CLI) are appropriate for the stated purpose.
Instruction Scope
All runtime instructions are limited to installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to Agenty via Membrane. The instructions do not ask the agent to read unrelated files, env vars, or system state. Note: the SKILL.md tells the user to perform a global npm install and to authenticate via browser; those are expected for a CLI-based integration but worth user review.
Install Mechanism
There is no automated install spec in the registry; the documentation tells users to run `npm install -g @membranehq/cli`. Using a public npm package is common, but global npm installs require elevated rights and install code from a third-party package — the skill itself does not ship code, so this is the primary install risk to evaluate manually.
Credentials
The skill declares no required environment variables or config paths. The SKILL.md explicitly advises letting Membrane manage credentials rather than asking for API keys locally, which is proportionate to the described functionality.
Persistence & Privilege
The skill does not request always:true or any elevated persistence. It's user-invocable and allows autonomous invocation (platform default). It does not instruct modifying other skills or global agent configuration.
Assessment
This skill is instruction-only and coherent with its stated purpose, but before using it: 1) Verify the authenticity and reputation of the @membranehq/cli npm package (check the npm page and GitHub repo) before running `npm install -g` (global installs modify your system and may require elevated permissions). 2) Understand that authentication opens a browser and delegates access to Membrane — confirm you're comfortable granting Membrane access to your Agenty account and review its privacy/security docs. 3) Prefer installing in isolated or non-critical environments if you’re unsure (use a container or dedicated VM). 4) If you need stronger assurance, inspect the Membrane CLI source code or run it in a sandbox before granting access to production data.Like a lobster shell, security has layers — review code before you run it.
latestvk970g13988wyz7m4fahkke3d05843xk2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.