Name: honeybadger
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

honeybadger

Honeybadger integration. Manage Organizations, Users. Use when the user wants to interact with Honeybadger data.

Quality

65%

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/honeybadger/SKILL.md

Quality

Content

68%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 body is highly actionable with copy-paste CLI commands and a solid connection-state workflow, but it carries introductory concept explanations Claude already knows and lacks verification guidance for its destructive actions. Splitting the large actions table into a reference file would further improve organization.

Suggestions

Remove or trim the opening "Honeybadger is an error and uptime monitoring tool..." paragraph and other concept explanations to assume Claude's prior knowledge.

Add a verification step after destructive/batch action runs (e.g. re-list the project or confirm state) to establish a validate-then-proceed feedback loop.

Move the Popular actions table into a references/ file (e.g. ACTIONS.md) and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and tables, but it opens with an explanatory paragraph defining what Honeybadger is ("error and uptime monitoring tool for developers... used by software engineers and DevOps teams") and includes explanatory asides about Membrane auth — concepts Claude already knows — so it lands at the score-3 "mostly efficient but includes some unnecessary explanation" anchor.	3 / 5
Actionability	It provides copy-paste-ready executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a concrete actions table with keys and JSON parameter examples, matching the score-5 "fully executable; copy-paste ready" anchor.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and --wait polling), but the skill exposes destructive operations (delete-project, update-fault) with no verification step after running, and the rubric's destructive-ops cap therefore limits workflow_clarity to 3.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no deep or broken references (no bundle files exist), but the sizeable Popular actions table is inlined rather than split into a reference file, leaving it at the score-4 "good structure with minor organization gaps" anchor rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

61%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 distinct and includes an explicit use-when trigger, but it undersells the skill's real capabilities by listing only Organizations and Users with the generic verb "Manage" and omits the natural task terms (faults, errors, uptime). Tightening the capability list and trigger phrasing would raise specificity and trigger-term quality.

Suggestions

Replace the generic "Manage Organizations, Users" with concrete actions that match the body, e.g. "List and manage Projects, Faults, Occurrences, Uptime Checks, and Users in Honeybadger."

Expand the trigger to natural user phrasing: "Use when the user wants to view Honeybadger errors/faults, triage exceptions, or check uptime monitoring."

Drop or sharpen "Honeybadger integration" opener so the description leads with capabilities rather than a label.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Honeybadger integration") and two entities ("Organizations, Users") but the only verb is the generic "Manage" and it omits the core objects shown in the body (Projects, Faults, Occurrences, Uptime Checks), so actions are minimal/generic — closer to the score-2 anchor than the score-3 concrete-action anchor.	2 / 5
Completeness	It supplies both a "what" ("Manage Organizations, Users") and an explicit "when" clause ("Use when the user wants to interact with Honeybadger data"), but the "when" is generic and the "what" is narrow, so it falls at the score-4 anchor rather than the fully-explicit score-5 anchor.	4 / 5
Trigger Term Quality	It surfaces the natural brand keyword "Honeybadger" via "Use when the user wants to interact with Honeybadger data", but misses the task terms users actually say (errors, faults, exceptions, uptime, check-ins), so keyword coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	Naming a specific branded product ("Honeybadger") with a single dedicated trigger gives it a clear niche and minimal overlap with other skills, matching the score-5 "clear niche with distinct triggers" anchor.	5 / 5
	Total	14 / 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/honeybadger/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.