Parsehub
v1.0.2ParseHub integration. Manage Projects. Use when the user wants to interact with ParseHub data.
⭐ 0· 123·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the instructions: the SKILL.md explains how to manage ParseHub projects via Membrane. Required actions (installing a Membrane CLI, creating a connector, invoking actions or proxying requests) are coherent with a ParseHub integration.
Instruction Scope
Instructions are focused on using the @membranehq/cli to authenticate, discover connectors/actions, run actions, and proxy requests to the ParseHub API. They do not ask the agent to read unrelated files, environment variables, or system configuration, nor to exfiltrate data to arbitrary endpoints. The guidance explicitly advises against asking users for API keys and to let Membrane handle credentials.
Install Mechanism
The skill is instruction-only (no install spec), but it instructs the user/agent to run `npm install -g @membranehq/cli`. Installing a global npm package executes code from the npm registry (moderate risk) — this is expected for a CLI-based integration but is the main surface to evaluate (verify package publisher, version, and integrity).
Credentials
The skill requests no local env vars or credentials; instead it requires a Membrane account and browser-based login. This is proportionate, but it means you must trust Membrane to hold and manage your ParseHub credentials and to proxy API requests on your behalf.
Persistence & Privilege
The skill is not always-enabled and is user-invocable; it does not request persistent privileges or attempt to modify other skills or system-wide configuration. Autonomous invocation is allowed by platform default but not combined here with other concerning flags.
Assessment
This skill is internally consistent: it tells the agent to install and use the official-looking Membrane CLI to connect to ParseHub and does not request unrelated credentials or files. The practical risks are: (1) installing a global npm package runs code from the npm registry — verify the @membranehq/cli package (publisher, version, and reviews) before installing; (2) using the skill requires a Membrane account and grants Membrane access to your ParseHub data via a connector — only proceed if you trust Membrane's service and security practices; (3) avoid copying ParseHub API keys into chat or other places — follow the connector/browser auth flow the skill describes. If you want to reduce risk, inspect the npm package source, run the CLI in an isolated environment, or create a dedicated ParseHub account with limited data access before connecting.Like a lobster shell, security has layers — review code before you run it.
latestvk97004dmm3kb4dxs2hxnsse95h842asn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.