Logz Io
v1.0.2Logz.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Logz.io data.
⭐ 0· 73·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
medium confidencePurpose & Capability
Name and description match the runtime instructions: the skill uses Membrane to interact with Logz.io. Required capabilities (network, Membrane CLI) are consistent with managing Logz.io data.
Instruction Scope
SKILL.md instructs the agent/user to install and use the @membranehq/cli, run membrane login (browser authentication), create connections, run actions, and proxy raw API requests via membrane request. These instructions stay within the stated purpose but route all requests and authentication through Membrane, which has privacy/third-party implications.
Install Mechanism
This is an instruction-only skill (no install spec). The doc tells users to run `npm install -g @membranehq/cli` or use npx; that is a normal, expected step but does introduce an external package installation step that the user must trust.
Credentials
No environment variables, credentials, or config paths are requested by the skill itself. The SKILL.md explicitly instructs not to collect API keys and to rely on Membrane to manage credentials server-side.
Persistence & Privilege
The skill is not always-enabled and does not request elevated persistence. It does enable autonomous invocation by default (platform normal), but that alone is not a red flag here.
Assessment
This skill is coherent: it uses the Membrane CLI to access Logz.io rather than asking for Logz.io API keys locally. Before installing or using it, confirm you trust Membrane (getmembrane.com/@membranehq and the npm package name). Understand that your log data and credentials will be routed through Membrane’s service — consider privacy, compliance, and least-privilege for any Logz.io account you connect. When installing the CLI, prefer official sources and verify package identity (package name, homepage, repository). If you need to avoid third-party proxying for regulatory reasons, do not use this skill and instead use a direct Logz.io integration that you control.Like a lobster shell, security has layers — review code before you run it.
latestvk972xknhm4x537ymybh0py6zr9843fd7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.