CtrlK
BlogDocsLog inGet started
Tessl Logo

ui-eng-vision-local-lit-renderer

Migrates legacy imperative DOM construction to local declarative Lit-html templates rendered inside existing containers.

55

Quality

69%

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-local-lit-renderer/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.

This is a strong, dense operational skill: it delivers concrete project-specific guidance with explicit validation loops (build/test per micro-commit, 0% visual-diff gate, self-audit checklist) and clearly signaled external references. Its main weaknesses are that the 13 numbered items are topical rules rather than a strictly sequenced workflow with the mandatory doc read buried mid-list, and a small amount of emphasis repetition could be trimmed.

DimensionReasoningScore

Conciseness

The body is dense with project-specific, non-obvious rules (clang-format boundaries, Gerrit moved-block behavior, the 'nothing' sentinel, HTMLElement casts) and assumes competence, with only minor spots that could be trimmed such as repeated emphasis phrases and the Mental Audit checklist restating earlier rules.

4 / 5

Actionability

Guidance is mostly executable — a concrete import ('import {html, render, nothing}'), a copy-ready cast example ('render(this.template(), this.containerField as HTMLElement)'), an explicit variant binding, and a concrete CSS selector migration ('.data-grid' to 'devtools-data-grid') — but there is no complete end-to-end worked example.

4 / 5

Workflow Clarity

Validation checkpoints are explicit ('Verify with build and run tests after each micro-commit', 'Any visual diff (above 0%)... is unacceptable', the 4-item audit checklist, wait-for-confirmation), so the batch-operation cap does not apply; however the 13 items read as topical rules rather than a strictly ordered sequence, and the mandatory doc read is buried at item 4.

4 / 5

Progressive Disclosure

The body is well-sectioned with clearly signaled, one-level-deep external references ('MANDATORY: You MUST read and load ui_engineering.md', the migration script path), and with no bundle files present all guidance inlined in SKILL.md is reasonable, though the component-mapping detail could live in a reference file.

4 / 5

Total

16

/

20

Passed

Description

50%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 gives a clear, specific statement of what the skill does, but it omits any 'when to use' trigger guidance, is jargon-heavy without natural user phrasings, and does not convey the Pass 2 scoping that would distinguish it from sibling migration skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when migrating a DevTools view's imperative DOM builders to Lit-html templates in place (Pass 2, after consolidation).'

Include natural phrasings/synonyms users would actually say, such as 'convert to templates', 'declarative rendering', or 'Lit migration', alongside the technical terms.

State the pass sequencing or prerequisite context (after Pass 1 consolidation) to reduce conflict risk with sibling migration skills.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions ('Migrates legacy imperative DOM construction to local declarative Lit-html templates' rendered 'inside existing containers'), but coverage is not comprehensive, matching the anchor for 1-2 concrete actions rather than the several-action 4 anchor.

3 / 5

Completeness

It clearly answers 'what' (migrate imperative DOM construction to local Lit-html templates) but has no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords are present ('imperative DOM', 'Lit-html', 'templates', 'containers') but they lean technical and miss natural user phrasings and synonyms like 'migrate rendering' or 'convert to templates', so coverage sits just below the 4 anchor.

3 / 5

Distinctiveness Conflict Risk

The Lit-html local-rendering niche is somewhat specific, but the body identifies this as 'Pass 2' of a multi-pass migration and the description omits that scoping, leaving real overlap risk with sibling migration skills.

3 / 5

Total

12

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 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.