Peach
v1.0.0Peach integration. Manage data, records, and automate workflows. Use when the user wants to interact with Peach data.
⭐ 0· 49·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
The name/description (Peach integration) match the instructions, which direct the agent to use the Membrane CLI to connect to Peach and run actions or proxied requests. Minor inconsistency: the 'Official docs' URL points at developers.helpshift.com/ios/peach which appears unrelated to Membrane/Peach and may be a bad link or copy/paste error.
Instruction Scope
SKILL.md stays on-task: it instructs installing and using the Membrane CLI, discovering connectors/actions, running actions, and proxying requests to the Peach API. It does not instruct reading arbitrary local files or asking for unrelated secrets. Note that using the proxy lets Membrane see request/response data and handle credentials server-side (expected for this integration).
Install Mechanism
This is instruction-only (no install spec), but it tells the user to install a global npm package: `npm install -g @membranehq/cli`. That is a standard install method; the package is scoped to @membranehq which reduces risk compared to an arbitrary unscoped package. Because installation is left to the user, verify the package and registry before installing.
Credentials
The skill declares no required env vars or local credentials and explicitly instructs to let Membrane handle auth rather than asking for API keys. That is proportionate to an integration skill.
Persistence & Privilege
The skill is not always-enabled and uses normal autonomous invocation defaults. It does not request elevated or persistent system-wide privileges.
Assessment
This skill appears coherent: it only contains instructions to install and use the official Membrane CLI to connect to Peach and run actions. Before installing or using it: 1) Verify the @membranehq/cli package and its publisher on npm (scoped packages are better than unscoped but still review versions). 2) Confirm you trust Membrane as a third-party proxy for your Peach data — Membrane will handle authentication and will see proxied request/response data. 3) Note the odd 'Official docs' link (helpshift) — treat that as a documentation error and check the real Peach API docs or the Membrane connector docs on getmembrane.com. 4) Prefer installing in controlled environments (avoid unknown global package installs on critical systems). If you need higher assurance, request the connector implementation or a repository link from the publisher to review the exact actions and data flows.Like a lobster shell, security has layers — review code before you run it.
latestvk9769v49mn67yj6b30wy8g530s84dy2r
License
MIT-0
Free to use, modify, and redistribute. No attribution required.