Locoia

v1.0.2

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

0· 86·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 match the instructions: the skill details how to use the Membrane CLI to connect to and operate on Locoia data. Required capabilities (network, Membrane account/CLI) are appropriate for this integration.
Instruction Scope
SKILL.md instructs running the Membrane CLI, creating connections, listing actions, and proxying requests to Locoia. These steps are within the stated scope, but they imply that Membrane (a third-party service) will see proxied API traffic and handle credentials — a privacy/trust consideration for users.
Install Mechanism
This is an instruction-only skill (no install spec). It recommends installing @membranehq/cli via npm or using npx. That is a common approach, but installing a global npm package modifies the host environment and users should verify the package provenance before installing.
Credentials
The skill requests no environment variables or local secrets and explicitly delegates auth management to Membrane. The lack of extra credential requests is proportionate and appropriate.
Persistence & Privilege
The skill does not request always-on presence, does not alter other skills' configs, and does not demand elevated persistence or privileges.
Assessment
This skill appears coherent: it teaches the agent to use the Membrane CLI to connect to Locoia and perform actions. Before installing/use: verify the @membranehq/cli package on npm (or prefer npx to avoid a global install), confirm you trust Membrane as the proxy (they will see API requests and manage credentials), and be cautious before running action run or request commands that could modify production data — inspect action IDs, input JSON, and connectors first. If you need stricter data control, consider whether direct authenticated access to Locoia (instead of proxying) better fits your security requirements.

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

latestvk978c5fdgxmd2x358a3s5sg2d1842h9a

License

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

Comments