CtrlK
BlogDocsLog inGet started
Tessl Logo

ui-eng-vision-widget-promoter

Promotes legacy views to modern UI.Widget classes, hooks up performUpdate() rendering, and exports default views.

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/ui-eng-vision-widget-promoter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, actionable migration guide with concrete code examples, a clear step sequence, and an explicit self-audit checklist. It scores consistently strong across dimensions with only minor trimming and validation-loop gaps preventing top marks.

Suggestions

Tighten the opening paragraph to avoid restating the description, and condense explanatory notes to lean on Claude's existing knowledge of the widget framework.

Make the verification loop explicit (e.g. 'run build/tests, if failing review screenshot diffs and fix, re-run until green') rather than leaving it as a self-audit question.

Define or reference viewInput/viewOutput construction so the performUpdate example is fully executable without inference.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence, but the opening paragraph restates the description and a few explanatory sentences ('Note that VBox and HBox inherit...') could be trimmed, fitting score 4 rather than the lean score-5 anchor.

4 / 5

Actionability

Multiple concrete, copy-paste TypeScript examples (DEFAULT_VIEW export, INJECT pattern, performUpdate override, devtools-widget entry) cover the main migration steps, but minor gaps like undefined viewInput/viewOutput and template placeholders keep it just below fully executable score 5.

4 / 5

Workflow Clarity

A clear three-step sequence is paired with a Safety & Verification section and a Mental Audit checklist including a build/test checkpoint, but the validate-fix-retry loop is only implicit rather than an explicit recovery workflow, matching score 4.

4 / 5

Progressive Disclosure

Content is well-organized into labeled sections with one-level-deep, clearly signaled references to ../ui-widgets/SKILL.md and docs/ui_engineering.md, but some detailed code patterns remain inline that could be split out, fitting score 4 over the fully split score-5 anchor.

4 / 5

Total

16

/

20

Passed

Description

62%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 conveys a clear, specific set of actions for a niche codebase migration but omits any 'when to use' trigger guidance, capping its completeness and limiting natural trigger terms. It is distinctive but would benefit from explicit usage triggers.

Suggestions

Add a 'Use when...' clause naming natural user triggers, e.g. 'Use when migrating legacy DevTools views to UI.Widget classes or wiring up performUpdate() rendering.'

Include more natural phrasings or synonyms users might say (e.g. 'modernize views', 'widget migration', 'refactor panels') alongside the technical terms.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Promotes legacy views to modern UI.Widget classes', 'hooks up performUpdate() rendering', 'exports default views') with only minor coverage gaps, fitting the score-4 anchor rather than 3 (which expects just 1-2 actions) or 5 (which demands comprehensive coverage).

4 / 5

Completeness

The 'what' is clearly stated across three actions, but there is no 'when' or 'Use when...' trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Keywords like 'legacy views', 'UI.Widget', and 'performUpdate()' are domain-relevant but heavily technical jargon a user would not naturally vocalize, and no common synonyms or variations are present.

3 / 5

Distinctiveness Conflict Risk

The narrow DevTools widget-migration niche ('UI.Widget classes', 'performUpdate() rendering', 'default views') is highly specific with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
ChromeDevTools/devtools-frontend
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.