CtrlK
BlogDocsLog inGet started
Tessl Logo

repro-admin

Reproduce an EmDash admin UI bug. Boots a demo with bgproc, drives the admin with agent-browser using the dev-bypass session, and captures the reproduction as screenshots plus a written 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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 lean, fully actionable, and well-structured, with an explicitly sequenced procedure and validation checkpoints throughout. It assumes Claude's intelligence and gives copy-paste-ready commands with concrete operational caveats, hitting the top anchor on every dimension.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it gives exact commands and operational caveats without explaining what React, a dev server, or an accessibility snapshot is, so every token earns its place.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands with exact flags and arguments (e.g. 'bgproc start -n demo -w -- pnpm --filter ./demos/simple dev' and 'agent-browser snapshot -i -c'), plus concrete interaction primitives like 'click @e<n>'.

3 / 3

Workflow Clarity

The 8-step procedure is clearly sequenced with explicit validation checkpoints — waiting for the port to open (step 3), checking console/errors after each interaction (step 7), and rejecting non-matching broken states as non-reproductions (step 8) — giving feedback loops for error recovery.

3 / 3

Progressive Disclosure

This is a self-contained skill under 50 lines with no bundle files, organized into clear sections (Hard prohibitions, Procedure, When to skip, Output), which the rubric allows to score 3 on well-organized sections alone when no external references are needed.

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 clearly distinct, naming concrete actions and product-specific tooling that make its niche obvious. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness and leaves trigger-term coverage short of full.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when reproducing or confirming an EmDash admin UI bug reported in an issue.'

Broaden trigger terms to cover natural variations a user might say, such as 'admin bug', 'reproduce a UI issue', or 'confirm a reported admin defect'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Boots a demo with bgproc', 'drives the admin with agent-browser', and 'captures the reproduction as screenshots plus a written transcript' — matching the multi-action anchor rather than the partial-coverage level below.

3 / 3

Completeness

Clearly answers 'what does this do' but provides no explicit 'Use when...' trigger, so per the guideline capping completeness at 2 when trigger guidance is missing or only implied it cannot reach the what-and-both-when anchor.

2 / 3

Trigger Term Quality

Contains relevant natural terms ('reproduce', 'admin UI bug', 'screenshots') but lacks broad coverage of common variations and leans on product-specific tooling names, so it sits at 'some relevant keywords but missing common variations' rather than the full-coverage anchor.

2 / 3

Distinctiveness Conflict Risk

The combination of 'EmDash admin UI bug', 'bgproc', 'agent-browser', and 'dev-bypass session' carves a specific niche with distinct triggers that is unlikely to conflict with other skills.

3 / 3

Total

10

/

12

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.