Jitsu

v1.0.2

Jitsu integration. Manage data, records, and automate workflows. Use when the user wants to interact with Jitsu data.

0· 72·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (Jitsu integration) match the runtime instructions: the SKILL.md describes using the Membrane CLI to manage Jitsu connections, actions, and proxy requests. Required network access and a Membrane account are sensible and proportional.
Instruction Scope
Instructions are limited to installing/using the @membranehq/cli, authenticating via Membrane, listing/connecting to Jitsu connectors, running actions, and proxying requests. They do not request reading unrelated files, exporting secrets, or sending data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill (no install spec). The only install step in SKILL.md is a public npm global install (@membranehq/cli), which is a standard package install and expected for a CLI-based integration.
Credentials
The skill declares no required environment variables or credentials. The doc explicitly instructs to let Membrane manage credentials (no local API keys requested). This is proportionate to the described behavior, though it does depend on trusting Membrane's service.
Persistence & Privilege
Skill does not request always:true, does not modify other skills, and has no install-time components. Default autonomous invocation is permitted but not accompanied by broad credential access or privileged persistence.
Assessment
This skill appears coherent and low-risk: it instructs using the official-looking @membranehq/cli to access Jitsu via a Membrane account. Before installing, verify the @membranehq/cli package and the Membrane service (homepage/repo) are legitimate and up-to-date. Be aware that npm -g installs may require elevated privileges on your machine. Also consider whether you trust Membrane to proxy and manage your Jitsu credentials, since the CLI will cause authentication flows to hit their service.

Like a lobster shell, security has layers — review code before you run it.

latestvk971p556gmvw86s3nfhmndzk2h8438p1

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments