Followup
v1.0.2Followup integration. Manage Organizations, Users. Use when the user wants to interact with Followup data.
⭐ 0· 140·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
high confidencePurpose & Capability
Name/description align with the instructions: the SKILL.md tells the agent to use the Membrane CLI to manage Followup connectors, actions, and proxy requests. There are no unrelated environment variables or credential requests.
Instruction Scope
Instructions direct running the Membrane CLI (login, connect, action list/run, request proxy). This is within scope. Minor inconsistency: registry metadata lists no required binaries, but the runtime docs clearly require the 'membrane' CLI (install via npm). The SKILL.md does not instruct reading unrelated files or exfiltrating data.
Install Mechanism
No formal install spec in the registry; the README instructs installing @membranehq/cli via 'npm install -g'. Global npm installs are expected here but carry typical risks (verify package identity and permissions).
Credentials
The skill requests no environment variables or local secrets and explicitly tells integrators to let Membrane manage credentials rather than asking for API keys. This is proportionate for a connector-based integration.
Persistence & Privilege
Flags show no forced always-on presence and model invocation is allowed (the normal default). The skill does not request system-wide config changes or access to other skills' credentials.
Assessment
This skill is instruction-only and uses the Membrane CLI to access your Followup account via browser-based authentication. Before proceeding: (1) verify you trust https://getmembrane.com and the npm package @membranehq/cli (check the publisher and package versions on npm/GitHub); (2) be aware the CLI opens a browser for auth and Membrane will manage tokens server-side — ensure you are comfortable with that delegation; (3) installing the CLI globally requires appropriate permissions on your machine and should be done in a controlled environment; (4) note the minor metadata mismatch (the skill doesn't declare 'membrane' as a required binary even though the docs require it). If you need tighter control, consider using Membrane only on a machine/account you trust or inspect the Membrane CLI repository before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk972t2f302xr4nrzsbcehhgymh842nv5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.