Thru
v1.0.0Thru integration. Manage data, records, and automate workflows. Use when the user wants to interact with Thru data.
⭐ 0· 55·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 skill is described as a Thru integration and all runtime steps use the Membrane CLI to discover connectors, create connections, run actions, and proxy API requests to Thru. No unrelated credentials, binaries, or configuration paths are requested.
Instruction Scope
SKILL.md provides concrete CLI commands (installing and using @membranehq/cli, login flows, action listing/running, and proxy requests). It does not instruct reading unrelated system files or harvesting local env vars; the scope is limited to interacting with Membrane/Thru via the CLI.
Install Mechanism
The skill is instruction-only (no install spec), but it tells the user to install the Membrane CLI via npm (npm install -g @membranehq/cli or npx). This is an expected step for this integration but does require trusting the @membranehq npm package and installing a global CLI.
Credentials
No environment variables or local secrets are requested. The instructions explicitly advise against asking for API keys and rely on Membrane to manage credentials and token refresh server-side, which is proportional.
Persistence & Privilege
The skill does not request permanent presence (always:false), has no install-time hooks in the package, and does not modify other skills or system-wide agent settings. It's instruction-only and requires interactive authentication via the Membrane login flow.
Assessment
This skill looks coherent for integrating with Thru through Membrane. Before installing or following the SKILL.md: 1) Confirm you trust the @membranehq npm package and the Membrane service (check the homepage and GitHub repo). 2) Be prepared to authenticate via a browser (or use the headless login flow); the Membrane account will mediate access to Thru. 3) Installing a global CLI requires npm access and elevated package scope on your machine—follow your org's policy for third-party CLIs. 4) Understand that the CLI can proxy arbitrary Thru API calls on your behalf, so grant the connection only the permissions you intend. 5) If you need higher assurance, verify the upstream repository and package contents before installation. If you want me to, I can fetch the referenced GitHub repo and summarize what the Membrane CLI package contains (would require network access).Like a lobster shell, security has layers — review code before you run it.
latestvk97ewhp538cndk67ph73e8p0r9848vp9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.