CtrlK
BlogDocsLog inGet started
Tessl Logo

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, 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 body is a tightly written, highly actionable runbook with concrete commands, clear sequencing, and built-in validation and skip conditions. It is self-contained and well-organized with no need for external references.

DimensionReasoningScore

Conciseness

Largely lean and directive, assuming Claude's competence (no explaining what React or a browser is); a few operational asides could be trimmed slightly but most earn their place.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands (astro dev --background, agent-browser open with the exact dev-bypass URL, agent-browser snapshot -i -c, click/fill/select with @e<n> refs) covering the common reproduction cases.

5 / 5

Workflow Clarity

An explicit 8-step sequence with validation checkpoints (setup-failure handling in step 3, per-interaction JS error checks in step 7, failure-mode confirmation in step 8) and feedback loops for error recovery.

5 / 5

Progressive Disclosure

A single-purpose, self-contained skill with no bundle files and well-organized sections (Environment, Do not, Procedure, When to skip, Output); the simple-skill exception applies and the body is appropriately structured.

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, actionable, and distinctive, clearly conveying the reproduction workflow. Its main weakness is the absence of an explicit 'when to use' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reproducing a reported EmDash admin UI bug from an issue, or when the user asks to reproduce an admin UI regression.'

Include natural synonyms users might say ('admin console bug', 'repro', 'regression') to broaden trigger coverage.

Mention the expected outcome (confirmed reproduction vs. could-not-reproduce) so the 'when' framing is concrete.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Attach a container', 'start the demo dev server', 'drive the admin with agent-browser', 'capture the reproduction as screenshots plus a replayable transcript' — covering the full reproduction workflow comprehensively.

5 / 5

Completeness

The 'what' is clear and concrete, but there is no explicit 'Use when...' clause or equivalent trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural phrases a user would say are present ('Reproduce an EmDash admin UI bug', 'screenshots', 'replayable transcript'), but a few common synonyms and trigger variations are missing, so it sits just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to 'EmDash admin UI bug' reproduction with tool-specific terms (agent-browser, dev-bypass session), giving it a clear niche with minimal conflict risk against other skills.

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.