CtrlK
BlogDocsLog inGet started
Tessl Logo

repro-public

Reproduce a bug in the public-facing rendered site (not the admin). Attach a container, start the demo dev server, drive public routes with agent-browser, and capture the reproduction as screenshots plus a replayable transcript.

69

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 highly actionable with a well-sequenced, checkpointed workflow and clean section structure. Only minor conciseness trims would improve it.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but a few explanatory sentences (e.g. the misidentification aside in step 9) could be trimmed slightly.

4 / 5

Actionability

Copy-paste-ready commands appear throughout — `agent-browser open "http://localhost:4321/<path>"`, `astro dev --background`, `pnpm exec emdash content create <collection> --data '...'` — covering the common reproduction cases.

5 / 5

Workflow Clarity

A clear numbered 1–9 sequence includes explicit validation checkpoints: setup-failure handling in step 4, 'Confirm the failure mode matches' in step 9, and a 'When to skip' section as a feedback/escape loop.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files, yet is organized into well-signaled sections (Environment, Do not, Procedure, When to skip, Output), meeting the simple-skill exception for a top score.

5 / 5

Total

19

/

20

Passed

Description

75%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 specific and well-differentiated, but it omits an explicit 'Use when...' trigger clause, capping its completeness. Adding concrete trigger phrases would round it out.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks to reproduce a bug on the public site, or reports rendering/routing/RSS/sitemap issues a visitor would see.'

Include natural synonyms users say (e.g. 'repro', 'regression', 'public pages') alongside 'Reproduce a bug' to broaden trigger coverage.

Clarify 'agent-browser' as a trigger only if users actually name it; otherwise keep it as a mechanism rather than a keyword.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Attach a container, start the demo dev server, drive public routes with agent-browser, and capture the reproduction as screenshots plus a replayable transcript' — giving comprehensive coverage of the reproduction workflow.

5 / 5

Completeness

The 'what' is clear, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

'Reproduce a bug' is a natural user phrase, but coverage lacks synonyms or file extensions and leans on jargon like 'agent-browser', so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

'public-facing rendered site (not the admin)' carves out a clear niche and explicitly disambiguates from an admin-reproduction skill, minimizing conflict risk.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
emdash-cms/emdash
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.