Checkmarket
v1.0.2CheckMarket integration. Manage data, records, and automate workflows. Use when the user wants to interact with CheckMarket data.
⭐ 0· 77·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 (CheckMarket integration) match the actual instructions: all runtime steps call the Membrane CLI to connect to CheckMarket, list actions, run actions, or proxy API requests. Requested capabilities are appropriate for the stated purpose.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI and performing CheckMarket-related operations (login, connect, list/run actions, proxy requests). It does not ask to read unrelated files, export environment variables, or exfiltrate data to unexpected endpoints beyond Membrane (the documented proxy).
Install Mechanism
There is no automated install spec in the registry (instruction-only). The doc recommends installing @membranehq/cli globally via npm (npm install -g). This is reasonable for a CLI-based integration but is a user-side action that installs third‑party code on the machine; consider using npx or auditing the package on npm before global install.
Credentials
The skill declares no required env vars or credentials (Membrane handles auth). This is proportionate to the purpose, but important privacy implication: API calls and authentication tokens will be routed through Membrane's service (per the docs), so sensitive survey data and credentials are handled server-side by a third party.
Persistence & Privilege
always is false and there are no config-path or system-wide modifications in the instructions. The skill does not request persistent system privileges beyond recommending a CLI be installed by the user.
Assessment
This skill is coherent and appears to do what it says: it teaches using the Membrane CLI to manage CheckMarket data. Before installing/using it: (1) understand that Membrane acts as a proxy — API calls and credentials will be handled by Membrane servers, so review their privacy/security policies and confirm you’re allowed to send the survey data there; (2) prefer npx @membranehq/cli@latest for one-off use or audit the @membranehq/cli package on npm before globally installing it; (3) the login flow opens a browser (or prints a URL for headless flows) — follow your org’s guidance for authenticating third‑party CLIs; (4) no environment variables or local secrets are requested by the skill itself, but be cautious about what accounts you connect through Membrane.Like a lobster shell, security has layers — review code before you run it.
latestvk97fcejeevpd9yptnt24rqqpn1842yzz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.