Loggly
v1.0.0Loggly integration. Manage data, records, and automate workflows. Use when the user wants to interact with Loggly data.
⭐ 0· 55·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 (Loggly integration) match the instructions, which consistently show how to use the Membrane CLI to authenticate, create a Loggly connection, run actions, and proxy API requests. Nothing requested is unrelated to integrating with Loggly.
Instruction Scope
Instructions stay within Loggly/ Membrane functionality (login, connection, action discovery, proxy requests). They do instruct the agent/user to use Membrane as a proxy for API calls, which is expected for this integration, but has privacy/ data-flow implications because log payloads will transit Membrane's service.
Install Mechanism
This is an instruction-only skill (no install spec). The SKILL.md recommends installing @membranehq/cli via npm (-g). That is a standard public npm install but will install a global binary and run the package's install scripts; users should vet the package and publisher before installing globally.
Credentials
The skill declares no required env vars or credentials and relies on Membrane's browser-based login/connection flow. That is proportional to the stated purpose. The docs explicitly advise against collecting API keys locally, which reduces unnecessary credential requests.
Persistence & Privilege
The skill is not marked always:true and is user-invocable; it does not request elevated platform privileges or modify other skills. Autonomous invocation (disable-model-invocation: false) is the platform default and not, by itself, a concern here.
Assessment
This skill is a usage guide for the Membrane CLI to interact with Loggly and appears coherent. Before installing or using it: (1) confirm you trust Membrane (getmembrane.com) because API requests and log payloads will pass through their service; logs can contain sensitive data and secrets, so review their privacy/security policy and the OAuth scopes requested at login; (2) inspect the npm package (@membranehq/cli) and its publisher before running a global npm install; (3) consider using an isolated account or staging environment first and avoid sending highly sensitive logs through third-party proxies; (4) prefer org-managed credentials and least-privilege connections where possible.Like a lobster shell, security has layers — review code before you run it.
latestvk973768g7na99ex67dqths7mnh84bdcg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.