Alchemer

v1.0.2

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

0· 100·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
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Alchemer integration) matches the instructions: all runtime actions are calls to Membrane which proxies Alchemer. No unrelated credentials, binaries, or paths are requested.
Instruction Scope
SKILL.md instructs the agent to install and use the Membrane CLI, create a Membrane connection to Alchemer, list/run actions, and optionally proxy raw API requests. It does not instruct reading arbitrary local files or exfiltrating unrelated environment variables. It requires network access and a Membrane account, which is consistent with the proxy model.
Install Mechanism
There is no included install spec, but the doc recommends installing @membranehq/cli via npm -g. Installing a global npm package is a normal install path but does execute third-party code on the machine; the user should verify the package/maintainer before installing.
Credentials
The skill declares no required env vars or local credentials. It explicitly directs use of Membrane-managed connections rather than asking the user for API keys, which is proportionate to its purpose.
Persistence & Privilege
The skill is user-invocable, not forced-always, and allows autonomous invocation (the platform default). There is no request to modify other skills or global agent settings.
Assessment
This skill appears coherent, but take basic precautions: verify you trust Membrane/getmembrane.com and the @membranehq npm package before installing a global CLI (review the npm package and the GitHub repo linked in SKILL.md). Understand that Membrane will handle and store the Alchemer credentials for proxying—only proceed if you trust that vendor and their scope of access. If possible, use least-privilege Alchemer accounts or restrict connection scopes. Finally, avoid pasting sensitive keys into chat; follow the documented browser-based login/connection flow.

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

latestvk97erxxmt504pfb8bzx4v1v0k1843dpv

License

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

Comments