repro-public

Reproduce a bug in the public-facing rendered site (not the admin). Boots a demo with bgproc, drives the public routes with agent-browser, and captures the reproduction as screenshots plus a written transcript.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is tight, executable, and well-structured: concrete commands, a sequenced procedure with explicit validation checkpoints, and clean single-level references. It is a strong, self-contained skill body with no notable weaknesses.

Dimension	Reasoning	Score
Conciseness	The body is lean and imperative with concrete tool invocations and no padded explanations of concepts Claude already knows, matching the 'every token earns its place' anchor.	3 / 3
Actionability	Steps provide fully executable commands with exact flags and paths (e.g. 'bgproc start -n demo -w -- pnpm --filter ./demos/simple dev' and 'agent-browser snapshot -i -c'), which are copy-paste ready.	3 / 3
Workflow Clarity	A clear 9-step sequence includes explicit validation/error checkpoints (step 7 console/errors checks and step 9 'Confirm the failure mode matches') with a feedback loop for misidentification recovery.	3 / 3
Progressive Disclosure	A single well-organized SKILL.md uses clear sections and only one-level-deep references ('consult skills/emdash-cli/SKILL.md' and '.bot-artifacts/' outputs), with no nested reference chains.	3 / 3
	Total	12 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 specific and well-differentiated, naming concrete tools and actions, but it lacks an explicit 'when to use' trigger clause and natural user-facing keywords. Adding a 'Use when...' clause with common variations would raise the trigger-term and completeness scores.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when reproducing a bug on the public site, rendering issues, sitemap/RSS, or public routing'.

Include common user-facing keywords (e.g. 'public site', 'rendered page', 'reproduction steps', 'screenshots') alongside the tool names.

Consider phrasing a few actions in plain terms a reporter might use, so trigger matching does not depend on 'bgproc'/'agent-browser' jargon.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Boots a demo with bgproc', 'drives the public routes with agent-browser', 'captures the reproduction as screenshots plus a written transcript' — matching the rubric's 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers what the skill does but lacks any 'Use when...' or equivalent explicit trigger guidance, so per the rubric completeness is capped at 2.	2 / 3
Trigger Term Quality	Contains some natural terms ('bug', 'public-facing rendered site', 'screenshots') but leans on tooling jargon ('bgproc', 'agent-browser') and omits common user-facing variations, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	'public-facing rendered site (not the admin)' carves a clear niche and explicitly disambiguates from admin-reproduction skills, making it unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: emdash-cms/emdash
Path: .flue/skills/repro-public/SKILL.md
Commit: 53dbf22

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