Logsnag
v1.0.2LogSnag integration. Manage Insights, Users, Projects. Use when the user wants to interact with LogSnag data.
⭐ 0· 115·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
high confidencePurpose & Capability
Name/description (LogSnag integration) align with instructions: everything centers on using Membrane to connect to LogSnag, discover actions, run actions, or proxy API requests. No unrelated credentials, binaries, or system access are requested.
Instruction Scope
Instructions ask the agent/user to install and use the Membrane CLI, perform a browser-based login, create connections, list actions, run actions, and proxy requests. This is within scope for a LogSnag integration, but it does route LogSnag requests and credentials through Membrane—so data and auth are handled by a third-party service rather than locally.
Install Mechanism
No install spec in the registry; SKILL.md recommends installing @membranehq/cli via npm (global install). This is a common pattern but carries the usual npm/global install risks and requires trusting the package published as @membranehq/cli.
Credentials
The skill declares no required environment variables or credentials. The SKILL.md explicitly instructs not to ask users for LogSnag API keys and instead use Membrane connections, which is proportionate to the stated purpose.
Persistence & Privilege
Skill is instruction-only, has no install step that modifies agent config, and always:false. Agent autonomous invocation is allowed (platform default) and appropriate for this integration.
Assessment
This skill is instruction-only and consistent with its description, but it depends on the Membrane service and installing the @membranehq/cli package. Before using: verify you trust Membrane (review privacy, security, and repository links), prefer using npx to avoid a global npm install if you want to reduce persistence, be aware that LogSnag data and connector credentials will flow through Membrane (they can see proxied requests), and revoke connections when no longer needed. If you need tighter control, consider integrating directly with LogSnag using your own API keys rather than routing through a third-party proxy.Like a lobster shell, security has layers — review code before you run it.
latestvk97632wbat17z1mzm298a2yzp5843fjj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.