Name: bugzilla
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

bugzilla

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

Quality

61%

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

Quality

Content

61%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 strongly actionable with executable Membrane CLI commands and a well-validated connection workflow, but it carries some redundant concept explanation and omits verification guidance for the data operations it enables. Adding a post-action validation step and trimming the Bugzilla intro would improve conciseness and workflow clarity.

Suggestions

Add a verification/check step after running actions (e.g. re-query or inspect the `output` field to confirm the bug change took effect) to satisfy the destructive/batch validation expectation.

Remove or condense the "Bugzilla is a web-based bug tracking system..." introductory paragraph and other explanatory padding that Claude already knows.

Include at least one worked, Bugzilla-specific example (e.g. searching for a bug by ID and updating its status) with concrete parameter values.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational commands, but it includes unnecessary explanation Claude already knows (the two-sentence "Bugzilla is a web-based bug tracking system..." intro) and padded prose ("so you can focus on the integration logic rather than auth plumbing").	3 / 5
Actionability	Concrete, copy-paste-ready commands cover the common cases (install, login, connection ensure, action list/run, request proxy), with only a minor gap: no worked Bugzilla-specific example showing a real action invocation with concrete parameters.	4 / 5
Workflow Clarity	The connection setup is well-sequenced with polling and state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but running actions against bug records can be destructive or batch and the skill provides no validation/verification step after action execution, capping this dimension at 3.	3 / 5
Progressive Disclosure	The single SKILL.md is organized into clear, well-labeled sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references, though at ~140 lines some detail (e.g. connection-state handling) could be split into a reference file.	4 / 5
	Total	14 / 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 has an explicit "Use when" trigger and a distinct Bugzilla niche, but its capability statement is generic ("manage data, records, automate workflows") rather than naming concrete Bugzilla actions. Tightening the action list and adding natural trigger terms would raise specificity and trigger quality.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete Bugzilla actions, e.g. "Search and file bugs, update bug status, add comments, and query defect reports."

Add natural trigger terms users actually say, such as "bugs", "issues", "defects", or "file a bug", alongside "interact with Bugzilla data".

Dimension	Reasoning	Score
Specificity	The description names the Bugzilla domain but its actions are generic — "Manage data, records, and automate workflows" lists no concrete Bugzilla operations (e.g. file bugs, query issues, update status).	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Bugzilla data") are present, though the "what" is generic rather than concrete.	4 / 5
Trigger Term Quality	"Bugzilla" and "interact with Bugzilla data" are relevant keywords, but common natural variations users would say ("bugs", "issues", "defects", "file a bug", "track bugs") are missing.	3 / 5
Distinctiveness Conflict Risk	"Bugzilla integration" targets a clear, specific product niche with a distinct trigger ("Bugzilla"), giving minimal overlap risk with other skills.	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/bugzilla/SKILL.md
Commit: f484c82

Reviewed: 3 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.