Chatlayer

v1.0.2

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

0· 95·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
Name and description match the instructions: all commands and steps relate to using Membrane to interact with Chatlayer. No unrelated services or credentials are requested.
Instruction Scope
SKILL.md limits actions to installing and using the Membrane CLI, creating connections, listing actions/connections, running actions, and proxying requests to the Chatlayer API. It does not instruct reading arbitrary local files or accessing unrelated environment variables.
Install Mechanism
The skill is instruction-only (no install spec), but it tells users to install @membranehq/cli globally via npm. That is an expected way to use the described workflow, but installing a global npm package executes third-party code—users should validate the package/source before installing.
Credentials
No environment variables or credentials are required by the skill. The instructions explicitly advise creating a connection through Membrane rather than asking users for API keys, which is proportionate to the stated purpose.
Persistence & Privilege
The skill is not always-enabled, and it does not request persistent system privileges or modifications to other skills. It relies on the Membrane CLI and user-driven login flows (browser-based auth).
Assessment
This skill is instruction-only and coherent: it tells you to install and use the Membrane CLI to connect to Chatlayer and explicitly avoids asking for raw API keys. Before installing the npm package (@membranehq/cli), confirm you trust the Membrane project (check the npm package page, GitHub repo, and homepage), prefer installing in a controlled environment (container or VM) if you are unsure, and avoid pasting sensitive credentials into third-party tools. If you need higher assurance, review the @membranehq/cli source code or use an environment where you can audit network calls during the first run.

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

latestvk97ftxzbw7p4dgpmqk3b732h35843b6m

License

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

Comments