validate-ui

Comprehensive end-to-end validation of the Archon Web UI using browser automation and codebase review. Use when: User wants to validate, test, or audit the Archon web interface, find UI/UX bugs, test workflow management, verify parallel agent orchestration, or run comprehensive browser-based E2E tests. Triggers: "validate ui", "test the ui", "e2e test", "browser test", "validate archon", "test archon ui", "ui audit", "ux review", "comprehensive test", "validate everything". Capability: Starts Archon, runs exhaustive browser automation tests via agent-browser CLI, performs codebase review, and produces a detailed bug/UX report. NOT for: Unit tests (use `bun test`), CLI-only validation (use /validation:validate-simple).

Quality

92%

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

85%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.

A thorough, highly actionable E2E validation runbook with clear sequencing, validation checkpoints, and concrete commands. Its main weakness is progressive disclosure: all content sits in one large file with no reference structure to keep the overview lean.

Suggestions

Move the Phase 2 file-review tables and the Phase 3 report template into reference files (e.g. references/file-review-checklist.md, references/report-template.md) and link to them from SKILL.md so the main file reads as a lean overview.

Consolidate the 'Execution Notes' section — it restates re-snapshot, screenshot, and npx-fallback guidance already covered in Phase 1 — to trim redundancy.

Consider summarizing the 9 test suites inline with one-line descriptions and moving the full per-test steps into references/test-suites.md, reducing inline footprint while preserving the actionable detail.

Dimension	Reasoning	Score
Conciseness	The 645-line body is dense with distinct, actionable test cases rather than explanations of concepts Claude already knows, but the Execution Notes section restates guidance from Phase 1 and some 'Verify:' lists could be tightened.	4 / 5
Actionability	Copy-paste-ready bash commands (pkill, lsof, curl health checks, agent-browser open/snapshot/screenshot/set viewport) and concrete per-test interaction steps cover the common cases with specific, executable guidance.	5 / 5
Workflow Clarity	Clearly sequenced Phase 0-3 with explicit validation checkpoints (port-free verification, backend/frontend health curls, test-data existence check), a feedback directive ('If a test fails, document it immediately and continue'), and a 6-category review checklist.	5 / 5
Progressive Disclosure	Well-organized into numbered phases and suites, but it is a 645-line monolith with no bundle files or one-level-deep references; the large file-review tables and report template that could live in reference files are inlined.	3 / 5
	Total	17 / 20 Passed

Description

100%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.

An exceptionally well-structured description that explicitly separates what, when, triggers, capability, and negative guidance, all in third-person voice. It is comprehensive, concrete, and clearly distinguishable from sibling validation skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions in third person — 'Starts Archon, runs exhaustive browser automation tests via agent-browser CLI, performs codebase review, and produces a detailed bug/UX report' — giving comprehensive coverage with no vague padding.	5 / 5
Completeness	Explicitly answers both what ('Comprehensive end-to-end validation of the Archon Web UI using browser automation and codebase review') and when ('Use when: User wants to validate, test, or audit...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Ten explicit trigger phrases ('validate ui', 'test the ui', 'e2e test', 'browser test', 'ui audit', 'ux review', etc.) plus natural 'Use when' variants cover the synonyms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Scoped to the Archon Web UI niche with a 'NOT for: Unit tests (use bun test), CLI-only validation (use /validation:validate-simple)' clause that explicitly disambiguates from neighboring skills, minimizing conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (662 lines); consider splitting into references/ and linking	Warning
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	13 / 16 Passed

Repository: coleam00/Archon
Path: .claude/skills/validate-ui/SKILL.md
Commit: d1ada87

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