CtrlK
BlogDocsLog inGet started
Tessl Logo

bugherd

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

53

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/bugherd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 delivers concrete, executable Membrane CLI commands with a reasonably clear connection-setup workflow and validation checkpoints, but it is weighed down by a 20-row action table whose entries all say "No description" and some loose numbering.

Suggestions

Replace or trim the "Popular actions" table whose every row reads "No description" — either populate real descriptions or link to where action schemas can be discovered.

Fix the step numbering: the text references "Step 2" and "1b" but those labels are not consistently applied to the corresponding sections.

Move the long proxy-options flag table or the popular-actions list to a referenced file if the skill grows, to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient executable commands, but the 20-row "Popular actions" table where every row says "No description" is noise, and filler like "Use action names and parameters as needed" could be trimmed.

3 / 5

Actionability

Provides copy-paste-ready commands (install, login, connection ensure, action list/run, request) with flags and JSON examples covering common cases, with only minor gaps such as placeholder CONNECTION_IDs and undescribed action rows.

4 / 5

Workflow Clarity

A clear install → authenticate → connect → poll-for-ready → search → run sequence exists with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), though the "Step 2" / "1b" numbering is inconsistent and unlabeled.

4 / 5

Progressive Disclosure

A self-contained skill with well-organized sections and no need for bundle files; structure is good, but the inline 20-row action table and the dangling external docs URL are minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

52%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 correctly uses third person and includes an explicit "Use when" trigger tied to a distinctive product name, but its capability statement is generic ("manage data, records, and automate workflows") and lacks concrete BugHerd-specific actions and synonyms.

Suggestions

Replace the generic "Manage data, records, and automate workflows" with concrete BugHerd actions, e.g. "List and create tasks, projects, comments, and columns."

Add natural synonyms users might say, such as "bug reports", "visual feedback", or "issue tracking" alongside "BugHerd data".

Tighten the "Use when" clause to mention specific scenarios, e.g. "Use when the user wants to manage BugHerd tasks, projects, or comments."

DimensionReasoningScore

Specificity

It names the domain ("BugHerd integration") but the actions are generic and minimal ("Manage data, records, and automate workflows") rather than concrete BugHerd-specific operations like tasks, projects, or comments.

2 / 5

Completeness

A "Use when..." clause is present ("Use when the user wants to interact with BugHerd data"), but the "what" is vague ("Manage data, records, and automate workflows") rather than a clear statement of concrete capabilities.

3 / 5

Trigger Term Quality

"BugHerd" and "interact with BugHerd data" are natural product-name triggers, but common variations or synonyms (bugs, feedback, issue tracking, tasks) are absent.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product "BugHerd" gives it a clear niche with distinct triggers and minimal risk of conflicting with other skills.

5 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.