CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reproduce-bug-report

Reproduce a UI bug report before coding and capture visual evidence. Trigger: reproduce this bug, bug report.

Quality

77%

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 ./ywai/skills/reproduce-bug-report/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 a strong, highly actionable orchestration skill with concrete agent-call templates, a complete shared child prompt, explicit error-recovery checkpoints, and a defined output format. Its main weakness is redundancy — several safety and version-matching rules are stated multiple times — and its single-file bulk could be reduced by moving child prompt boilerplate to reference files.

DimensionReasoningScore

Conciseness

The body is mostly efficient for a multi-agent orchestration skill, but key guidance is repeated — the "screen recording by default, screenshots as supplement" rule appears three times (shared child prompt, artifact workflow, and success criteria), and reporter-version matching guidance is restated across "Version and app setup", child prompt steps 2-3, and "Report back" — fitting 'mostly efficient but could be tightened' rather than the minor-trim profile of 4.

3 / 5

Actionability

The skill is fully executable for an instruction-only orchestration task: a concrete `run_agents` call shape with parameters, a copy-paste-ready shared child prompt with explicit placeholders, three named child prompt patterns (primary, variant, code-path hypothesis), a manifest specification, and a summary format template covering the common cases.

5 / 5

Workflow Clarity

Both levels have clear sequences with explicit checkpoints and error-recovery branches: the 6-step parent workflow includes decision points (single vs multiple agents, constraint reporting), and the 11-step child workflow contains stop conditions and feedback loops ("If the bug appears, stop changing variables", "make at most two targeted variations", "If the app crashes, hangs, or blocks progress, capture a screenshot"), plus a status taxonomy and report checklist.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so the skill is intentionally self-contained with well-organized, clearly headed sections; the minor gap is that at ~190 lines the ~70-line shared child prompt boilerplate is content that could be split into a reference file, keeping it at 'good structure, minor organization gaps' rather than fully clear splitting at 5.

4 / 5

Total

17

/

20

Passed

Description

62%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 answers both what and when with concrete trigger phrases and stays concise, but its action coverage is thin (two verbs) and its trigger list is narrow. Expanding both slightly would move it into the top tier.

Suggestions

Add one or two more concrete capabilities to the description, e.g. "Launch computer-use agents, capture a screen recording or screenshots, and report confirmed/non-reproduction with exact steps."

Broaden the trigger terms to cover natural variations users would say, such as "repro this", "reproduce this issue", "verify this bug", or "does this bug reproduce".

Scope the trigger to the skill's actual domain (UI/visual bugs) to reduce overlap with general bug-triage or debugging skills — e.g. "Use when the user reports a UI or visual bug and asks to reproduce it."

DimensionReasoningScore

Specificity

"Reproduce a UI bug report before coding and capture visual evidence" names the domain plus two concrete actions (reproduce, capture evidence), but stops there — no mention of recordings, screenshots, variants, or environment matching — fitting the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor at 4.

3 / 5

Completeness

Both parts are present: a clear 'what' ("Reproduce a UI bug report... and capture visual evidence") and an explicit 'when' via the "Trigger: reproduce this bug, bug report" clause with concrete trigger phrases. Not 5 because the when-clause is narrow — it omits 'UI' and issue/ticket phrasing — and not 3 because trigger guidance is explicitly stated rather than implied.

4 / 5

Trigger Term Quality

The triggers "reproduce this bug" and "bug report" are natural phrases a user would say, but only two are provided, missing common variations and synonyms such as "repro", "reproduce this issue", or "verify this bug", which matches 'some relevant keywords but missing common variations' rather than the good coverage of 4.

3 / 5

Distinctiveness Conflict Risk

Bug reproduction with visual evidence capture is a mostly distinct niche with clear triggers, but the bare trigger term "bug report" could also match bug-triage or general debugging skills, giving minor overlap risk with closely related skills rather than the minimal conflict risk of 5.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

YoizenSA/dev-ai-workflow

Path

ywai/skills/reproduce-bug-report/SKILL.md

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.