Linguixcom

v1.0.0

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

0· 53·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
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill name/description say it's a Linguix.com integration and all runtime instructions revolve around using the Membrane CLI to connect to Linguix, list actions, run actions, and proxy requests — these requirements match the stated purpose.
Instruction Scope
SKILL.md only instructs the agent to install/run the Membrane CLI, create connections via browser-based auth, list/run actions, and proxy API requests through Membrane. It does not instruct reading unrelated files or environment variables, nor does it instruct exfiltration of data to unknown endpoints.
Install Mechanism
There is no automated install spec in the registry (instruction-only skill), but the doc asks the user to run 'npm install -g @membranehq/cli' (and shows npx usage). Installing a global npm package is a reasonable step for a CLI-based integration, but it has the usual risks of installing third‑party npm packages globally — verify package provenance before installing.
Credentials
The skill declares no required env vars or credentials; authentication is delegated to Membrane (browser login / connection flow). It does not request unrelated secrets or access to other services.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It will run only when invoked; autonomous invocation is allowed by default (normal for skills) and is not combined with other high-risk factors.
Assessment
This skill is internally consistent: it simply directs use of the Membrane CLI to connect to Linguix. Before installing or using it, verify that '@membranehq/cli' and the referenced homepage/repository are the official project (to avoid typosquatting), prefer npx usage if you don't want a global install, inspect the package contents if you have concerns, and be prepared to complete browser-based authentication flows for the Membrane connection. If you need stronger assurance, confirm the skill publisher identity or use Membrane's official docs/CLI directly rather than trusting an unvetted registry entry.

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

latestvk976jxagkzdz5ebkqrfpc0qqmh84c95m

License

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

Comments