Clover

v1.0.2

Clover integration. Manage data, records, and automate workflows. Use when the user wants to interact with Clover data.

0· 99·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (Clover integration) align with the runtime instructions: the SKILL.md exclusively describes using the Membrane CLI to create a Clover connection, list/run actions, and proxy requests to Clover. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, logging in, creating/inspecting connections, running actions, and proxying Clover API calls. There are no steps that read arbitrary local files or request unrelated environment variables. Note: all proxied requests and credential handling occur via Membrane's service (expected for this integration).
Install Mechanism
This is an instruction-only skill (no install spec in registry), but SKILL.md tells users to install the Membrane CLI via npm install -g @membranehq/cli (or use npx). Installing a global npm CLI is common for this use case but carries the usual moderate risks of globally-installed packages; using npx avoids global installs.
Credentials
The skill declares no required env vars and relies on Membrane to manage credentials, which is proportionate for a connector-based integration. However, that means OAuth tokens/credentials for Clover will be stored/managed by Membrane — the user should evaluate and trust Membrane's account/permission model before connecting sensitive accounts.
Persistence & Privilege
Skill does not request always:true, does not claim persistence or modify other skills, and asks for no system configuration paths. Autonomous invocation is allowed (platform default) but not combined with elevated privileges here.
Assessment
This skill appears coherent: it uses the Membrane CLI to work with Clover and does not ask for local API keys. Before installing or using it: 1) Verify you trust Membrane (getmembrane.com) because OAuth credentials and proxied API calls will be handled by their service; 2) When installing the CLI prefer npx @membranehq/cli@latest to avoid a global npm install, or review the package before installing globally; 3) When creating the connector, review the permissions/scopes requested for your Clover account and limit access where possible; 4) Avoid pasting account secrets into chat — follow the connector/browser auth flow described in the SKILL.md.

Like a lobster shell, security has layers — review code before you run it.

latestvk97bas92f5kcym10k2hkntv6as843vye

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments