Outgrow

v1.0.0

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

0· 30·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill is described as an Outgrow integration and all runtime instructions focus on using the Membrane CLI to connect, list actions, run actions, and proxy requests to Outgrow. Requested network access and a Membrane account are proportional to the stated purpose.
Instruction Scope
SKILL.md instructs only CLI operations (installing/using @membranehq/cli, logging in via browser, creating connections, listing/running actions, and proxying requests). It does not instruct reading unrelated files, requesting unrelated credentials, or exfiltrating data outside the Membrane/Outgrow flow.
Install Mechanism
This is an instruction-only skill (no install spec provided). It tells users to install the Membrane CLI via npm (or use npx). Installing a global npm package is a normal mechanism here but carries the usual risks of third-party npm packages — verify the @membranehq package and its source before installing.
Credentials
The skill declares no required environment variables or config paths and explicitly advises not to ask users for Outgrow API keys (it relies on Membrane-managed auth). The level of credential access (Membrane account + browser auth) matches the functionality.
Persistence & Privilege
always is false and the skill does not request persistent system-wide privileges or modify other skills. Autonomous invocation (default) is allowed but that is normal for skills and not by itself a red flag here.
Assessment
This skill appears to do exactly what it says: use the Membrane CLI to manage Outgrow integrations. Before installing or using it, verify the @membranehq/cli package (check the npm page and GitHub repo), and review Membrane's privacy/security docs because Membrane will broker access to your Outgrow data. If you manage highly sensitive data, consider using an account with limited scope and double-check which actions/requests the agent runs. Finally, prefer npx if you want to avoid installing a global npm package, and inspect package source if you have security concerns.

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

latestvk973y0ewrks902fp3kn538ntrx846nqv

License

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

Comments