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

88%

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

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 content is highly actionable and well-sequenced with real validation checkpoints, but it is a long monolithic document that underuses progressive disclosure — the report template and codebase review tables would be better as separate reference files.

Suggestions

Move the Phase 3 report-format template and the frontend/backend codebase review file tables into reference files (e.g. references/report-template.md, references/codebase-review-checklist.md) and link to them one level deep, so SKILL.md stays an overview.

Tighten the 9 test suites' repetitive '- Verify:' bullet pattern into a compact checklist format to cut tokens while preserving the verifiable actions.

Since no bundle files exist yet, add at least a references/ file for the long review tables; a 650-line monolith with no external references misses the progressive-disclosure intent for a skill this size.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows (no 'what is SSE/markdown' prose) and is concrete throughout, but at ~650 lines it is long; the full Phase 3 report template and exhaustive per-file review tables are content Claude could generate on demand and could be tightened.	2 / 3
Actionability	Guidance is copy-paste ready: concrete bash (pkill/lsof/curl/agent-browser), exact URLs and routes, named components (WorkflowProgressCard, ParallelBlockView), and a step-by-step snapshot-refs workflow. Every test step is a specific verifiable action.	3 / 3
Workflow Clarity	Phases 0–3 are clearly sequenced with explicit validation checkpoints around the destructive setup — 'Verify ports are free', health check after backend start, frontend-serving check — and per-test 'If a test fails, document it immediately and continue' feedback guidance.	3 / 3
Progressive Disclosure	The body is well-sectioned into phases and test suites, but it is monolithic: no bundle files exist in references/scripts/assets, and large chunks that should be separate (the 30-row codebase review table, the report template) are inlined rather than linked one level deep.	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 specific, trigger-rich, and complete, cleanly answering what the skill does and when to use it while staying in third person and scoping out adjacent skills. It is a strong, low-conflict description.

Dimension	Reasoning	Score
Specificity	Multiple concrete actions are listed, e.g. 'runs exhaustive browser automation tests via agent-browser CLI, performs codebase review, and produces a detailed bug/UX report' alongside 'find UI/UX bugs' and 'verify parallel agent orchestration'.	3 / 3
Completeness	It clearly answers both 'what' ('Comprehensive end-to-end validation of the Archon Web UI using browser automation and codebase review' + Capability line) and 'when' (an explicit 'Use when' clause plus a Triggers list). Voice is third person ('User wants'), so no specificity penalty applies.	3 / 3
Trigger Term Quality	Explicit Triggers list natural phrases a user would say — 'validate ui', 'test the ui', 'e2e test', 'browser test', 'ui audit', 'ux review', 'validate everything' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	It targets a clear niche (Archon Web UI validation) and adds a 'NOT for' exclusion ('Unit tests... CLI-only validation use /validation:validate-simple'), making it unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 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: ace0a41

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