Push By Techulus
v1.0.2Push by Techulus integration. Manage data, records, and automate workflows. Use when the user wants to interact with Push by Techulus data.
⭐ 0· 140·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 describe interacting with Push by Techulus data and the SKILL.md consistently instructs the agent to use the Membrane CLI to discover connectors, create connections, run actions, and proxy API requests — all directly relevant to the stated purpose.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, authenticating via browser, listing/connecting actions, and proxying API requests through Membrane. This is coherent, but the proxy behavior means requests and data will flow through the Membrane service (not directly to Push by Techulus), which is a privacy/third‑party routing consideration the user should be aware of.
Install Mechanism
There is no packaged install spec in the registry; SKILL.md tells the user to npm install -g @membranehq/cli. Installing a global npm package is standard for CLI use but does download and run third‑party code from the npm registry — verify the package identity and origin before installing.
Credentials
The skill declares no required environment variables or local config paths. It relies on Membrane for auth and browser-based login, which matches the stated intent and does not ask for unrelated secrets.
Persistence & Privilege
The skill is instruction-only, not always-enabled, and does not request system-wide changes or modify other skills. Normal Membrane CLI usage may persist tokens/config locally (outside this skill), but the skill itself does not demand elevated persistence.
Assessment
This skill is coherent but relies on the Membrane service and a global npm CLI install. Before using: 1) Confirm you trust https://getmembrane.com and the npm package @membranehq/cli (check the package page and repository). 2) Understand that proxying via Membrane means request payloads and responses pass through their servers — don’t send highly sensitive data unless you’ve reviewed their privacy/security policies. 3) Be aware the CLI will perform a browser-based login and may store tokens locally; inspect or sandbox the CLI if you need to limit local persistence. 4) If you want extra assurance, review the Membrane CLI source code in the linked repository and verify connector IDs before creating connections.Like a lobster shell, security has layers — review code before you run it.
latestvk970fm1c2npqtn6tb4pwv6kpf184313w
License
MIT-0
Free to use, modify, and redistribute. No attribution required.