Serphouse
v1.0.2SERPhouse integration. Manage Organizations, Users. Use when the user wants to interact with SERPhouse data.
⭐ 0· 85·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 name/description (SERPhouse integration) match the instructions (use Membrane CLI to create connections, run actions, or proxy requests to the SERPhouse API). Nothing requested in the skill is unrelated to that purpose.
Instruction Scope
SKILL.md instructs the agent to install and use the Membrane CLI, log in (browser-based auth or headless code flow), list connections/actions, run actions, and proxy requests. It does not instruct reading unrelated local files or environment variables, nor does it tell the agent to exfiltrate data to unexpected endpoints. It does assume network access and a Membrane account.
Install Mechanism
No install spec is embedded in the skill bundle (instruction-only). The README suggests installing @membranehq/cli via npm -g. Using the public npm registry is expected for a CLI, but global npm installs have normal supply-chain and privilege considerations — review the package and prefer npx or a sandboxed environment if you have concerns.
Credentials
The skill declares no required env vars or credentials. It uses Membrane's managed auth flow (browser-based) rather than asking for API keys, which is proportionate to the stated purpose. The user must trust Membrane with SERPhouse credentials because Membrane acts as a proxy.
Persistence & Privilege
The skill is not always-included and does not request persistent elevated privileges or modify other skills. It relies on the Membrane CLI and network access only.
Assessment
This skill is coherent and appears to simply document using the Membrane CLI as a proxy to SERPhouse. Before installing or following the instructions: 1) Confirm you trust Membrane (https://getmembrane.com) because authentication is handled server-side through their service. 2) Prefer running the CLI via npx (@membranehq/cli@latest) or in a container/isolated environment rather than doing a global npm -g install, to reduce supply-chain risk. 3) Be aware the login step opens a browser (or headless flow) and grants Membrane access to your SERPhouse connection — do not share other local secrets. 4) If you need higher assurance, inspect the @membranehq/cli package source and review Membrane's privacy/security docs before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk979aekk2sb2736fexy8vxaw7x843dd9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.