CtrlK
BlogDocsLog inGet started
Tessl Logo

replicate-issue

Replicate and validate a GitHub issue by spinning up Archon, analyzing the issue, and systematically testing all described symptoms using browser automation. Use when: User wants to reproduce a bug, validate a GitHub issue, confirm a reported problem, or investigate whether an issue is real before working on a fix. Triggers: "replicate issue", "reproduce issue", "validate issue", "confirm bug", "test issue", "can you reproduce", "try to replicate", "verify the bug". Capability: Checks out main, pulls latest, starts Archon, reads the GitHub issue, then uses agent-browser to systematically test every symptom and produce a findings report. NOT for: Fixing issues (use /archon or /exp-piv-loop:fix-issue), general UI testing (use /validate-ui).

71

Quality

88%

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

77%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 body is a thorough, highly actionable multi-phase workflow with strong sequencing and validation checkpoints. Its weaknesses are minor redundancy that hurts conciseness and a monolithic structure with no progressive file-based disclosure for a skill of this length.

Suggestions

Remove the redundant "Execution Notes" bullets that restate earlier guidance (e.g., the agent-browser-not-Playwright rule is already stated in Phase 2) to tighten conciseness toward the score-3 anchor.

Extract the Phase 5 option format and the Phase 7 report template into bundled reference files (e.g., references/report-template.md) and link to them one level deep, improving progressive disclosure for this longer skill.

Consolidate the Testing Guidelines and Execution Notes lists, which overlap (both cover screenshot cadence, curl cross-referencing, and agent-browser usage), into a single concise checklist.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence (no explaining what a browser or git is), but it carries redundancy — the "Execution Notes" section restates earlier guidance ("Always use agent-browser ... NOT Playwright") and several guideline bullets could be trimmed, so it is not fully lean.

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands throughout — `git checkout main`, `gh issue view $ARGUMENTS --json ...`, `agent-browser open/snapshot/click`, and curl+jq snippets — matching the score-3 anchor for concrete executable guidance.

3 / 3

Workflow Clarity

A clearly sequenced Phase 0–7 workflow with explicit validation checkpoints (port-free verification, backend health curl, frontend-serving check) and feedback loops (re-snapshot after DOM changes, "If reproduced" branching), satisfying the score-3 anchor.

3 / 3

Progressive Disclosure

The skill is a single ~270-line monolithic file with no bundled reference files (references/scripts/assets absent); the only pointer is to an external skill (/agent-browser). Sections like the report template and option format are inline rather than split out, so it has structure but is not a lean overview pointing one level deep into separate files.

2 / 3

Total

10

/

12

Passed

Description

100%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 well-crafted: it states concrete capabilities, lists natural trigger phrases, explicitly answers both what and when, and clearly distinguishes itself from neighboring skills with a NOT-for clause. All four dimensions land at the top of the scale.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "spinning up Archon, analyzing the issue, and systematically testing all described symptoms" plus "Checks out main, pulls latest, starts Archon, reads the GitHub issue, then uses agent-browser" — matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (replicate/validate an issue) and when ("Use when: User wants to reproduce a bug, validate a GitHub issue...") with an additional "NOT for" exclusion clause, satisfying the what-AND-when anchor.

3 / 3

Trigger Term Quality

Provides eight natural trigger phrases users would say ("replicate issue", "reproduce issue", "validate issue", "confirm bug", "can you reproduce", "try to replicate", "verify the bug"), giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Scoped to a specific application (Archon) and a specific action (issue replication), with explicit exclusions for adjacent skills ("NOT for: Fixing issues... general UI testing"), giving it a clear niche unlikely to conflict.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
coleam00/Archon
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.