ui-eng-vision-logic-consolidator

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

Quality

60%

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

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 well-structured, actionable refactor workflow with concrete TypeScript patterns, explicit confirmation/validation checkpoints, and a self-audit checklist, with only minor intro redundancy to tighten.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and instructional with no padding about concepts Claude already knows, but the opening paragraph restates the frontmatter description and several bullets could be tightened, matching 'mostly efficient but could be tightened'.	2 / 3
Actionability	It gives concrete, specific guidance with real TypeScript snippets (state interface fields, lit-html render template) and named identifiers like performUpdate() and #updateSummaryBar(...), which for an instruction/refactor skill is copy-pattern-ready rather than vague.	3 / 3
Workflow Clarity	Six clearly sequenced steps include explicit checkpoints — a prefactoring pause for confirmation (step 5/6) and a Mental Audit checklist verifying minimal diffs, state completeness, and build — providing the validation feedback loop the rubric rewards.	3 / 3
Progressive Disclosure	The skill is a single self-contained SKILL.md with well-organized numbered sections and a checklist, no nested or missing references, so it meets the simple-skill bar for clean one-level organization.	3 / 3
	Total	11 / 12 Passed

Description

35%

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 states a clear, domain-specific capability but reads as technical jargon with no natural trigger terms and no 'Use when' guidance, so it answers 'what' but not 'when'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when refactoring imperative/lit-html UI code that manually builds or mutates the DOM in constructors or event handlers.'

Soften jargon with natural user terms (e.g. 'refactor', 'extract methods', 'UI state') so the description matches how a user would actually ask for it.

List a couple of distinct concrete actions (extract, consolidate, route through performUpdate) to lift specificity from one consolidated verb to multiple.

Dimension	Reasoning	Score
Specificity	Names a concrete domain (manual DOM creation, updates, constructors) and target artifacts (private helper methods, structured state interfaces), but effectively describes one consolidated action rather than multiple distinct concrete verbs, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	It clearly states what the skill does but omits any 'Use when...' or equivalent trigger guidance, so the 'when' is missing rather than explicit, capping completeness at 2 per the guideline.	2 / 3
Trigger Term Quality	Terms like 'DOM creation', 'constructors', 'helper methods', and 'state interfaces' are technical jargon a user would not naturally utter when requesting this skill; there are no natural-language trigger keywords.	1 / 3
Distinctiveness Conflict Risk	The DOM-to-state-interface refactor niche is somewhat specific, but without explicit triggers it could still overlap with general refactoring or UI-cleanup skills.	2 / 3
	Total	7 / 12 Passed

Validation

100%

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 — 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
Commit: 184a74d

Reviewed: 3 days 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.