Talenox
v1.0.2Talenox integration. Manage Persons, Companies. Use when the user wants to interact with Talenox data.
⭐ 0· 126·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 (Talenox integration) matches the instructions: all runtime guidance is about using Membrane CLI to connect to Talenox, run actions, or proxy requests. Nothing in the SKILL.md asks for unrelated cloud credentials or capabilities.
Instruction Scope
Instructions are focused on installing and using the @membranehq/cli to discover connectors/actions and proxy Talenox API calls. They instruct running CLI commands and opening a browser for auth (or completing headless flow). They do not instruct reading unrelated files or environment variables. Note: the agent is expected to run external CLI commands and network requests via Membrane.
Install Mechanism
There is no registry-level install spec; the SKILL.md recommends installing the Membrane CLI with `npm install -g @membranehq/cli`. That is a reasonable, common mechanism, but it is an instruction to install a global npm package rather than an automated install by the platform. Users should be aware they will need to install that package themselves and that installing global npm packages affects the host environment.
Credentials
The skill declares no required environment variables or credentials, which is consistent. However, runtime usage delegates authentication and credential storage to Membrane (a third‑party service). That means Talenox tokens and request payloads will transit through and be stored/managed by Membrane — this is expected for this design, but is a privacy/trust decision the user should consider.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system settings in its instructions, and requires no special config paths. It does rely on network access and an external account (Membrane), but it does not demand elevated platform privileges.
Assessment
This skill is internally consistent: it uses the Membrane CLI to connect to Talenox and does not ask for unrelated secrets. Before installing/use: 1) Confirm you trust Membrane (getmembrane.com) because your Talenox API calls and tokens will flow through their service; review their privacy/security and where data is stored. 2) Be aware you must install a global npm package (`@membranehq/cli`) yourself — you may prefer a local or containerized install to avoid changing host global packages. 3) When authenticating, verify the browser auth flow and connection IDs returned by Membrane. If you need to keep Talenox data purely within your infrastructure, this proxy‑through‑Membrane design may not be appropriate.Like a lobster shell, security has layers — review code before you run it.
latestvk974atfhrtckt2jsparj7p2s11843npk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
