Peepl
v1.0.0Peepl integration. Manage data, records, and automate workflows. Use when the user wants to interact with Peepl data.
⭐ 0· 63·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
The skill name/description (Peepl integration) matches the instructions: all runtime steps use the Membrane CLI to discover connectors, create connections, run actions, and proxy API calls to Peepl. Required network access and a Membrane account are reasonable and expected for this purpose.
Instruction Scope
SKILL.md stays within scope: it instructs installing and using the Membrane CLI, performing login (browser-based or headless), listing/connecting to Peepl connectors, running actions, and proxying requests. It does not ask the agent to read unrelated files, harvest local secrets, or send data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no install spec). The doc recommends installing @membranehq/cli via npm -g or using npx. Installing a global npm CLI is a normal, proportional step but carries the usual npm/package-supply-chain considerations; the skill itself does not automatically download or execute code.
Credentials
The skill declares no required env vars, no config paths, and no primary credential. Authentication is delegated to Membrane's browser/OAuth flow, which is consistent with the stated design and avoids local secret prompts.
Persistence & Privilege
The skill is not marked always:true and does not request persistent or system-wide configuration changes. It is user-invocable and allows normal autonomous invocation, which is the expected default for skills.
Assessment
This skill appears internally consistent, but before installing/running the Membrane CLI you should: 1) verify the @membranehq/cli package on npm and prefer npx (or pinned versions) over global -g installs to reduce system impact; 2) avoid running npm installs as root; 3) confirm getmembrane.com and docs.peepl.com are the official endpoints you trust, because authentication is handled server-side by Membrane and that service will have access to your Peepl tokens/data; 4) use a test/sandbox tenant or least-privilege account for initial trials; and 5) review any OAuth scopes or permissions presented during the browser login flow before consenting.Like a lobster shell, security has layers — review code before you run it.
latestvk97bkc4naw1jhx3dcdyvjqpag584b87b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.