ClawHub

Fattmerchant

v1.0.0

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

⭐ 0· 68·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill name/description (Fattmerchant integration) matches the SKILL.md: all instructions are about using the Membrane CLI to connect to and proxy requests to Fattmerchant. There are no requests for unrelated cloud credentials or unrelated system resources.
✓
Instruction Scope
SKILL.md contains concrete CLI workflows (installing membrane CLI, login, connect, action list/run, request proxy). It does not instruct the agent to read arbitrary files, environment variables, or system state beyond performing network/API operations via Membrane. The guidance to use Membrane as a proxy is consistent with the stated purpose.
ℹ
Install Mechanism
No install spec in the registry (instruction-only). The doc tells users to install @membranehq/cli via npm (global or npx). This is expected for a CLI-based integration, but installing an external npm package has the usual supply-chain considerations — verify the package identity and source before installing.
✓
Credentials
The skill declares no required env vars, no primary credential, and the instructions explicitly say not to ask users for API keys and to let Membrane manage credentials. That is coherent and proportional to the skill's purpose.
✓
Persistence & Privilege
always is false and the skill does not request persistent or system-wide changes. It is user-invocable and can be invoked autonomously per platform defaults; that is normal and not excessive here.
Assessment
This skill is instruction-only and relies on Membrane (https://getmembrane.com / @membranehq/cli) to proxy requests to Fattmerchant. Before using: (1) Confirm you trust the Membrane service and the npm package @membranehq/cli (check the publisher and repository), (2) be aware that data and API calls will flow through Membrane (they will handle authentication server-side), and (3) do not provide local API keys — follow the documented connection flow so Membrane manages credentials. If you need an offline or self-hosted integration, this skill does not provide that.

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

latestvk974mp8c3pxqrkxbwdhw606aws844c26

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments