ui-eng-vision-test-scaffolder

Scaffolds unit tests and screenshot tests to establish visual and functional rendering baselines for views before refactoring.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/ui-eng-vision-test-scaffolder/SKILL.md

Quality

Content

81%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 content is actionable and well-sequenced with strong validation checkpoints and feedback loops, scoring high on workflow clarity and actionability. Minor conciseness trims and optional reference extraction would push it toward the top anchors.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, instructional content without explaining concepts Claude already knows, but a few 'Why it is required' paragraphs and explanatory phrasing could be trimmed, keeping it just below the lean anchor 5.	4 / 5
Actionability	It provides concrete commands (cider script, npm run test, export PATH, npm run build) and an executable TypeScript screenshot-test snippet, with only minor template placeholders (username/workspace_name, mockViewInput) leaving small gaps.	4 / 5
Workflow Clarity	A clearly numbered lifecycle with explicit checkpoints ('Wait for confirmation'), a feedback loop in the screenshot-style flow, error-recovery scenarios (Scenario D), and a Mental Audit checklist match the anchor for explicit validation steps and feedback loops.	5 / 5
Progressive Disclosure	Well-organized sections (lifecycle, environment scenarios, mental audit) with content appropriately inline for a single-file skill, but it demonstrates no reference-splitting or one-level-deep navigation, so it sits below the textbook anchor 5.	4 / 5
	Total	17 / 20 Passed

Description

70%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, distinctive, and action-oriented, but it lacks an explicit 'Use when...' trigger clause, leaving the activation guidance only weakly implied. Adding concrete trigger phrasing would lift the completeness dimension.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when preparing to refactor or modernize view components and a visual/functional regression baseline is needed.'

Broaden trigger terms with synonyms users actually say, such as 'golden tests', 'screenshot/regression tests', and file extensions like '.test.ts'.

Enumerate the full action set (verify existing tests, detect coverage gaps, scaffold missing tests) to move specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('Scaffolds unit tests and screenshot tests', 'establish visual and functional rendering baselines') with only minor gaps in coverage, sitting just below the comprehensive anchor 5.	4 / 5
Completeness	The 'what' is clear, but the 'when' is only weakly implied via the temporal phrase 'before refactoring' with no explicit 'Use when...' trigger clause, so completeness is capped at 3 per the missing-trigger guidance.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('unit tests', 'screenshot tests', 'rendering baselines', 'views', 'refactoring') but missing common synonyms/extensions like 'golden tests', 'regression tests', or '.ts', so it falls short of the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	The niche is precise and trigger-specific (establishing visual/functional rendering baselines for views before refactoring), with minimal realistic overlap against other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: ChromeDevTools/devtools-frontend
Path: .agents/skills/ui-eng-vision-test-scaffolder/SKILL.md
Commit: 31f2967

Reviewed: ~16 hours 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.