Name: honeycombio
Rating: 60 (1 reviews)
Author: membranedev

honeycombio

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/honeycombio/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable CLI commands and a well-structured connection workflow featuring state-based checkpoints. It loses points mainly to an unnecessary intro explainer and minor redundancy/numbering gaps.

Suggestions

Cut the opening paragraph defining what Honeycomb.io is — Claude already knows the product — and start directly at the overview or setup.

Make step numbering consistent: label 'Step 1 connect', 'Step 1b wait', and an explicit 'Step 2 search/run actions' so the 'skip to Step 2' references resolve.

Deduplicate the action-discovery command, which appears verbatim in both 'Searching for actions' and 'Popular actions'.

Dimension	Reasoning	Score
Conciseness	Most of the body is concrete commands, but the opening paragraph ('Honeycomb.io is an observability platform that helps engineers understand and debug complex systems in production...') explains a concept Claude already knows, and the action-list command is restated across 'Searching for actions' and 'Popular actions'.	3 / 5
Actionability	Provides copy-paste-ready commands throughout — `npm install -g @membranehq/cli@latest`, `membrane connection ensure`, `membrane action list`, `membrane action run`, and a flags table for `membrane request` — covering the common install/auth/connect/run/proxy cases.	5 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence exists with explicit state-based checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but step numbering is inconsistent ('skip to Step 2' with no labeled Step 2) and action-run results lack a verification step.	4 / 5
Progressive Disclosure	Single-file skill (no bundle files) with well-organized section headers covering overview, setup, connection, actions, proxy, and best practices; content is mostly well-placed, though the proxy flags table and clientAction field reference could live in a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is third-person, names a distinct niche, and answers both what and when. Its main weakness is generic action verbs and thin trigger-term coverage that omits the observability vocabulary users would actually say.

Suggestions

Replace generic verbs with concrete Honeycomb actions, e.g. 'Query traces and spans, manage datasets and SLOs, run and analyze queries'.

Expand the trigger clause with natural terms users say: 'Use when the user wants to query observability data, investigate traces or spans, or manage Honeycomb.io datasets and SLOs.'

Add file-extension or product-specific synonyms (e.g. 'Honeycomb', 'observability', 'traces') to broaden trigger matching.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' — the domain is named and several actions are listed, but the actions are generic rather than concrete (no 'query traces', 'manage SLOs', 'inspect spans').	3 / 5
Completeness	Both what ('Honeycomb.io integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Honeycomb.io data') are present, but the when clause is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	The natural term 'Honeycomb.io' appears in 'Honeycomb.io integration' and 'interact with Honeycomb.io data', but common observability variations (observability, traces, spans, queries, SLOs, datasets) are missing.	3 / 5
Distinctiveness Conflict Risk	Targets a specific named product ('Honeycomb.io') with a distinct trigger, giving it a clear niche and minimal overlap with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/honeycombio/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.