Talkjs
v1.0.0TalkJS integration. Manage data, records, and automate workflows. Use when the user wants to interact with TalkJS data.
⭐ 0· 48·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
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (TalkJS integration) match the runtime instructions: the SKILL.md tells the agent to use the Membrane CLI to discover and run TalkJS actions and proxy API requests. Using a connector/proxy (Membrane) for a third-party service is coherent for this purpose.
Instruction Scope
Instructions are limited to installing the Membrane CLI, logging in, creating/listing connections, listing/running actions, and proxying API requests through Membrane. They do not instruct reading local files, harvesting environment variables, or contacting unrelated endpoints.
Install Mechanism
No install spec in registry (instruction-only). The SKILL.md recommends an npm global install (npm install -g @membranehq/cli). That is a reasonable, expected install path but carries the usual npm-global package considerations (verify package, avoid running as root).
Credentials
The skill requests no environment variables or config paths. It explicitly delegates auth to Membrane's login flow, which is appropriate for a connector-style integration and proportional to the stated purpose.
Persistence & Privilege
The skill is not always-enabled and is user-invocable. It does not ask to modify other skills or system-wide settings. Autonomous invocation remains allowed (default) but is not combined with broad credentials or unusual persistence.
Assessment
What to consider before installing: (1) This skill is an instruction-only guide that relies on the Membrane CLI (npm package @membranehq/cli) and a Membrane account — you'll be asked to run a browser-based login that grants Membrane access to TalkJS on your behalf. (2) Review and trust the Membrane service (getmembrane.com) and the npm package before installing globally; prefer installing in a virtual environment or with least-privilege. (3) Understand that API requests and chat data will flow through Membrane's servers (so verify their privacy/security posture and OAuth scopes). (4) There are no hidden env var requests or file reads in the documentation, but confirm the repository/package contents and review CLI prompts during login. (5) If you need stricter guarantees, test in a non-production account and inspect the Membrane CLI package source on GitHub/npm first.Like a lobster shell, security has layers — review code before you run it.
latestvk97bt6xjaexjqm2h8c7h32mga584abx1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.