Chatti
v1.0.0Chatti integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chatti data.
⭐ 0· 57·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 (Chatti integration) align with the instructions (use Membrane CLI to discover connectors, run actions, and proxy API requests to Chatti). Required capabilities (network, Membrane account) are appropriate for this purpose.
Instruction Scope
All runtime instructions focus on using the Membrane CLI to find connectors, run actions, and proxy Chatti API calls. One small ambiguity: the SKILL.md emphasizes that Membrane handles auth server-side with no local secrets, but it also instructs the user to run `membrane login` in a browser (a local CLI login flow). That is reasonable for OAuth-style flows, but users should understand the CLI will perform interactive login and may store local session state.
Install Mechanism
There is no automated install spec in the registry (instruction-only). The README advises installing `@membranehq/cli` globally via npm (`npm install -g @membranehq/cli`). This is a user-directed install (not performed automatically), which is expected for a CLI-based integration but does write software to the host if the user follows it.
Credentials
The skill declares no required env vars, config paths, or credentials. The SKILL.md explicitly advises not to ask users for API keys and to let Membrane manage auth, which is proportionate to the stated function.
Persistence & Privilege
The skill does not request always-on presence (always:false) and has default autonomous invocation settings. It does not ask to modify other skills or system-wide settings.
Assessment
This skill is instruction-only and appears coherent. Before installing/using it: (1) verify the Membrane CLI package (@membranehq/cli) is the official package you expect (check npm and the vendor homepage), (2) be aware `membrane login` performs an interactive browser OAuth flow and the CLI may store local session state or tokens, (3) do not share unrelated credentials — the skill intends Membrane to manage auth, and (4) if you have sensitive data, review Membrane's privacy/security docs and limit connector permissions or use a least-privilege account for the integration.Like a lobster shell, security has layers — review code before you run it.
latestvk97cbamz77d94e9ntmg0tjfajx84ev0b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.