CtrlK
BlogDocsLog inGet started
Tessl Logo

bugbug

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

58

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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 body is highly actionable with copy-paste-ready CLI commands and a well-structured connection state-machine, but it carries moderate prose padding and inconsistent step numbering that slightly weaken conciseness and workflow clarity. Progressive disclosure is good for a single-file skill though the embedded actions table leans reference-like.

Suggestions

Trim opinionated padding such as 'so you can focus on the integration logic rather than auth plumbing' and 'This will burn less tokens...' to tighten token efficiency.

Fix step numbering: add an explicit 'Step 1a' / 'Step 2' header so the 'skip to Step 2' and '1b' references resolve, and add a short validation note for executing actions on real runs.

Consider moving the 18-row Popular actions table into a references file or dropping the empty Description column to reduce inline reference bulk.

DimensionReasoningScore

Conciseness

Commands dominate and assume Claude's competence, but there is moderate padding (e.g. 'so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') and an 18-row actions table with empty description columns, matching the 'mostly efficient but includes some unnecessary explanation' anchor rather than the minor-only trimming of a 4.

3 / 5

Actionability

The body provides numerous copy-paste-ready executable commands covering connection setup, action search, action execution, and proxy requests with concrete flags, matching the fully-executable anchor that covers the common cases.

5 / 5

Workflow Clarity

The connection flow is a clear state-machine sequence with feedback loops (poll again after a client action), but step numbering is inconsistent ('skip to Step 2' with no Step 2 header, '1b' with no '1a'), there is no checklist, and no validation guidance for executing actions, matching the 'clear sequence with most checkpoints, minor gaps' anchor.

4 / 5

Progressive Disclosure

As a single-file skill with no bundle files, it is well-organized into clear, navigable sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices), with only minor gaps such as the inline reference-style actions table, matching the good-structure anchor.

4 / 5

Total

16

/

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 well-formed with an explicit 'Use when' clause and a clearly distinct named-tool trigger, but its action list is generic and it lacks concrete capability specifics or varied trigger phrases. It is solid but leaves room for sharper capability and trigger coverage.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete BugBug actions such as 'run tests and suites, list test runs, fetch run screenshots and status'.

Expand the trigger clause with concrete user phrases, e.g. 'Use when the user wants to run BugBug tests/suites, check run status, or fetch run screenshots'.

Add the file/term cues users actually say (e.g. 'test runs', 'suite runs', 'BugBug') to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names the BugBug domain but its actions ('Manage data, records, and automate workflows') are generic and abstract rather than concrete, matching the anchor for minimal/generic actions rather than the 1-2 concrete actions required for a 3.

2 / 5

Completeness

It answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with BugBug data'), but the trigger phrase is single and generic rather than the concrete multi-trigger phrasing that would warrant a 5.

4 / 5

Trigger Term Quality

'interact with BugBug data' includes the natural keyword 'BugBug' but offers only that single trigger with no synonyms or common variations, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'BugBug' is a specific named tool giving a clear niche with a distinct trigger and minimal risk of firing for unrelated skills, matching the clear-niche anchor.

5 / 5

Total

14

/

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.