Honeycombio
v1.0.0Honeycomb.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Honeycomb.io data.
⭐ 0· 48·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 promise Honeycomb.io integration and the SKILL.md consistently instructs using the Membrane CLI to connect, run actions, and proxy API calls to Honeycomb. No unrelated credentials, binaries, or config paths are requested. The npm-based CLI install and browser-based login are reasonable for this integration.
Instruction Scope
Runtime instructions stay on-topic: install/use @membranehq/cli, run membrane login, create/connect a Honeycomb connector, list/run actions, or proxy requests through Membrane. The instructions do not direct the agent to read unrelated files, harvest local secrets, or exfiltrate data to unknown endpoints. They do require network and interactive browser-based auth in typical flows.
Install Mechanism
There is no declared install spec in metadata, but SKILL.md advises running npm install -g @membranehq/cli. Installing a public npm package globally is a common but non-trivial action (writes to disk, requires privileges). The package is on npm/GitHub (traceable) — this is moderate risk compared to e.g., arbitrary downloads. Users should verify the package source before installing.
Credentials
The skill declares no required env vars or primary credential. It explicitly instructs not to collect Honeycomb API keys locally and instead to use Membrane's connection flow. This is proportionate: Membrane (a third party) will hold auth on the server side, so the only trust decision is about Membrane's access to your Honeycomb data.
Persistence & Privilege
always:false and default model-invocation settings are appropriate. The skill does not request persistent system-level privileges or modifications to other skills/configs. Autonomous invocation is allowed (platform default) and is not combined with other concerning privileges here.
Scan Findings in Context
[no_code_files_to_scan] expected: The package is instruction-only (SKILL.md only). The regex-based scanner had no code files to analyze, which is expected for an instruction-only skill. Absence of findings is therefore not evidence of additional safety; review of the commands and external packages referenced is the primary signal.
Assessment
This skill is a coherent guide for using Membrane's CLI to talk to Honeycomb.io. Before installing or following its steps: 1) Confirm you trust Membrane/@membranehq/cli (review the npm package and GitHub repo) because Membrane will manage your Honeycomb credentials server-side. 2) Installing the CLI with npm -g modifies your system — run in a controlled environment if concerned. 3) The skill uses browser-based login and will open or present URLs for auth; follow those flows rather than pasting secrets into the chat. 4) If you do not want a third party to hold your Honeycomb keys, do not use the Membrane connection flow and instead use a direct integration that matches your security requirements. Overall this skill looks internally consistent, but trust in Membrane as a service is the main external decision point.Like a lobster shell, security has layers — review code before you run it.
latestvk978v82xjyqg0fqvej1yv58vkh84fe1s
License
MIT-0
Free to use, modify, and redistribute. No attribution required.