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.

61

Quality

72%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, well-sequenced migration guide with concrete code templates and a verification checklist, structured cleanly with one-level-deep external references. Its main weakness is actionability: several code blocks contain placeholders or reference undefined fields that prevent them from being fully executable.

Suggestions

Replace the `html\`...\`` placeholder with a minimal concrete template (or explicitly justify the omission) so the DEFAULT_VIEW example is executable.

Define or annotate this.viewInput and this.viewOutput so the performUpdate override reads as complete rather than referencing undeclared members.

Consider moving the widget-framework rules detail into a bundled reference file under references/ and linking to it, now that the skill already points outside its own bundle for ../ui-widgets/SKILL.md.

DimensionReasoningScore

Conciseness

The body is lean and code-forward, assuming Claude's competence without explaining what UI.Widget or Lit are; the brief intro and section prose each earn their place.

3 / 3

Actionability

It supplies concrete TypeScript templates (DEFAULT_VIEW, INJECT constructor, performUpdate override, devtools-widget), but placeholders like `html\`...\`` and undefined this.viewInput/this.viewOutput leave key details missing, so it is not fully copy-paste ready.

2 / 3

Workflow Clarity

The three numbered guidelines give a clear sequence, and the closing 'Mental Audit' checklist plus the CRITICAL screenshot-golden rule provide explicit verification checkpoints including 'Does the code compile and do tests pass?'

3 / 3

Progressive Disclosure

No bundle files exist, so the score rests on organization: content is split into well-signaled sections with one-level-deep references (../ui-widgets/SKILL.md, docs/ui_engineering.md) rather than a monolithic wall of text.

3 / 3

Total

11

/

12

Passed

Description

60%

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 and third-person, clearly stating what the skill does, but it omits any 'when to use it' trigger guidance and leans on technical jargon over natural user terms. Adding a 'Use when…' clause with plainer triggers would raise completeness and trigger-term quality.

Suggestions

Append a 'Use when…' clause naming the situations that should trigger this skill (e.g., 'Use when migrating legacy SimpleView or custom wrapper panels to UI.Widget during the UI engineering pass').

Soften jargon with at least one natural trigger phrase a user might actually say, such as 'modernize legacy views' or 'convert a view to a Widget'.

Keep the concrete action list as-is; it is the strongest part of the description.

DimensionReasoningScore

Specificity

The description names three concrete actions — 'Promotes legacy views to modern UI.Widget classes', 'hooks up performUpdate() rendering', and 'exports default views' — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

It clearly answers 'what' (promote views, hook up rendering, export defaults) but provides no 'Use when…' or equivalent trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like 'legacy views', 'UI.Widget', and 'performUpdate() rendering' are domain-relevant but highly technical jargon, lacking the natural phrasings a user would say; missing common variations keeps it below a 3.

2 / 3

Distinctiveness Conflict Risk

The UI.Widget promotion niche is somewhat specific, but without explicit trigger guidance it could still overlap with other UI-migration subskills rather than being cleanly distinct.

2 / 3

Total

9

/

12

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.