ui-eng-vision-orchestrator

High-level orchestrator for managing multi-pass migration of Chrome DevTools legacy components to the modern UI engineering vision (UI.Widget & Lit-html).

Quality

63%

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-orchestrator/SKILL.md

Quality

Content

73%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 a well-structured, gated multi-pass orchestration workflow with strong sequencing, validation checkpoints, and a concrete plan template. Its main weaknesses are minor redundancy across the constraints and principles sections and a broken external reference with no supporting bundle files.

Suggestions

Remove the duplicated 'Strict Intermediate Stability' principle (#8) and the redundant API-update guidance, consolidating them into the Critical Constraints section to tighten conciseness.

Fix or remove the broken reference to ../../../docs/ui_engineering.md, or move the general principles into a local references/ file so the reference resolves within the skill bundle.

Consider splitting the per-pass detail and Structured Plan Template into a references/ file to improve progressive disclosure now that no bundle files exist.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and avoids explaining concepts Claude already knows, but 'Strict Intermediate Stability' is stated twice (constraint #2 and principle #8) and the constraints/principles sections overlap, so it could be tightened.	3 / 5
Actionability	Provides concrete orchestration guidance: a copy-pasteable Structured Plan Template, named subskills per pass, specific scan targets (ReportView, DataGrid, TreeOutline), and explicit trigger conditions, with only minor gaps since transform mechanics live in the subskills.	4 / 5
Workflow Clarity	A clearly sequenced gated multi-pass lifecycle (Plan, Scaffolding, Logic Consolidation, Lit Rendering, Widget Promotion) with per-pass trigger conditions, a user acceptance gate, explicit validation ('tests must pass after each step', halt-and-report), and a checklist — satisfying the destructive/batch feedback-loop requirement.	5 / 5
Progressive Disclosure	Well-organized sections with one clearly signaled one-level reference (ui_engineering.md) and named subskills, but no bundle files exist and the external doc path does not resolve to a real file.	4 / 5
	Total	16 / 20 Passed

Description

53%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 clearly conveys a specific, distinctive purpose but omits any 'when to use' trigger guidance, which caps completeness and weakens trigger-term quality. Adding an explicit 'Use when...' clause with natural phrasing would lift the weakest dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when modernizing Chrome DevTools legacy views, migrating imperative DOM to lit-html, or promoting views to UI.Widget.'

Add natural synonyms/variations users might say (e.g. 'Lit migration', 'Widget promotion', 'DevTools view modernization') to broaden trigger-term coverage.

Optionally list 1-2 more concrete actions (e.g. 'generates a gated migration plan and delegates Lit conversion and Widget promotion passes') to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('Chrome DevTools legacy components') and one concrete action ('managing multi-pass migration...to UI.Widget & Lit-html'), but does not enumerate several specific actions.	3 / 5
Completeness	The 'what' is clear, but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Relevant domain keywords appear ('migration', 'Chrome DevTools', 'Lit-html', 'UI.Widget') but they are technical and lack common synonyms, variations, or any natural 'Use when' phrasing.	3 / 5
Distinctiveness Conflict Risk	It targets a clear niche (Chrome DevTools legacy UI migration to UI.Widget/Lit-html) with minimal conflict risk, though the absence of explicit trigger phrasing leaves minor overlap with general DevTools modernization.	4 / 5
	Total	13 / 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
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

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

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