CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-eng-vision-logic-consolidator

Consolidates manual DOM creation, updates, and constructors into private helper methods and structured state interfaces.

Quality

67%

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-logic-consolidator/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 body is a tight, well-structured set of pipeline-specific refactoring rules with concrete identifiers, code fragments, an explicit user-confirmation gate, and a self-audit checklist. It assumes Claude's competence and avoids teaching known concepts. The main improvement opportunities are minor: a complete before/after example, an explicit build-verification command, and slight tightening of the later rules.

DimensionReasoningScore

Conciseness

The body is composed of directive, domain-specific rules ("Put the function signature around the existing code to minimize the diff", "The Gerrit Code Review UI cannot identify moved blocks of unchanged code") with no padding explaining concepts Claude already knows. This matches anchor 4 (efficient with minor trims possible): not 5 because the opening paragraph restates the description and rules 7-8 are wordy, and not 3 because there is no significant unnecessary explanation.

4 / 5

Actionability

Concrete identifiers and patterns appear throughout — "#updateSummaryBar(...)" or "#createEditorToolbar(...)", "performUpdate()" (with "Use this specific identifier"), "#renderSubtreeContent()", "splitWidget.uninstallResizer(...)" — plus two TypeScript snippets. This matches anchor 4 (mostly executable guidance with minor gaps): not 5 because the snippets are illustrative fragments and no complete before/after consolidation example is given, and not 3 because the directives name exact methods, variables, and identifiers to use.

4 / 5

Workflow Clarity

Rules 1-4 form an ordered pass (identify operations, isolate helpers, define state interface, extract rendering), rule 9 provides an explicit gate ("Wait for an explicit confirmation from the user"), and the Mental Audit checklist validates outcomes ("Does the code still compile?"). This matches anchor 4 (clear sequence with most checkpoints present): not 5 because validation is a self-audit with no concrete build command or error-recovery loop, and not 3 because the checkpoints (confirmation gate plus audit) are explicit rather than implicit.

4 / 5

Progressive Disclosure

The skill is a single self-contained file with clearly numbered rule sections and a separate audit section; no bundle files exist and the body references none, so nothing is buried or nested. This matches anchor 4 (good structure, appropriately placed content, minor organization gaps): not 5 because the ~110-line body exceeds the under-50-line simple-skill exception and rule clusters (e.g., the lit-html examples) could be split or tightened, and not 3 because all sections are clearly headed and no content that clearly belongs in a separate file is inlined.

4 / 5

Total

16

/

20

Passed

Description

42%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 in third person and states a clear, concrete capability, but it reads as jargon-heavy and covers only part of the skill's scope. It entirely lacks a "Use when..." trigger clause and natural-language keywords, capping completeness and trigger quality. Adding explicit trigger guidance and natural synonyms would substantially improve it.

Suggestions

Add an explicit 'Use when...' clause with natural triggers, e.g. "Use during lit-html or Logic First migration passes when refactoring imperative UI code, extracting helper methods, or preparing Gerrit prefactoring CLs."

Mention the skill's other concrete capabilities — routing updates through a single performUpdate() call, preserving imperative cleanup calls, and minimizing Gerrit review diffs — to broaden and sharpen the action list.

Include natural synonyms a user would actually say ("refactor UI code", "extract methods", "consolidate UI state") alongside the technical jargon to improve trigger term coverage.

DimensionReasoningScore

Specificity

"Consolidates manual DOM creation, updates, and constructors into private helper methods and structured state interfaces" names the DOM/UI domain and one concrete consolidation action, but omits major capabilities (lit-html render consolidation, performUpdate routing, Gerrit diff minimization). This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive): not 4 because it does not list several distinct specific actions, and not 2 because the actions named are concrete rather than generic.

3 / 5

Completeness

The description has a clear "what" ("Consolidates manual DOM creation, updates, and constructors into private helper methods and structured state interfaces") but no "when" — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because no invocation condition is present at all, and not 2 because the "what" is clear and specific.

3 / 5

Trigger Term Quality

The only keywords are technical jargon — "manual DOM creation", "private helper methods", "structured state interfaces" — with no natural phrases a user would say such as "refactor UI code", "extract helper methods", or "lit-html migration". This matches anchor 2 (one or two generic keywords, missing the natural phrases): not 1 because "DOM" and "helper methods" are relevant domain terms rather than entirely generic language.

2 / 5

Distinctiveness Conflict Risk

"Consolidates manual DOM creation, updates, and constructors into private helper methods and structured state interfaces" carves out a somewhat specific refactoring niche, but without trigger terms it could overlap with general code-refactoring or lit-html migration skills. This matches anchor 3 (somewhat specific but could still overlap with similar skills): not 4 because the overlap risk with closely related migration/refactoring skills is real, and not 2 because the description is not broadly generic.

3 / 5

Total

11

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ChromeDevTools/devtools-frontend

Path

.agents/skills/ui-eng-vision-logic-consolidator/SKILL.md

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.