CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

devtools-uistrings

Reviews added or modified UIStrings and localization (@description / @example) comments in Chrome DevTools for UX writing style, inline backtick locking, sentence case, UI glossary terminology, translator context, and sibling string consistency beyond what ESLint and check-strings.js enforce. Use when a CL or local diff adds or edits UIStrings or i18n calls in front_end/. Don't use for syntax rules already enforced by l10n ESLint rules or for unlocalized locked strings.

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

90%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.

A tightly written, highly actionable review checklist that wastes no tokens and gives exact, example-backed rules for every check. The only soft spots are the absence of an explicit processing order for a diff and the choice to keep a long terminology/glossary section fully inline in a single file.

DimensionReasoningScore

Conciseness

The body is a dense, telegraphic rulebook with zero concept explanations or filler — every bullet is a distinct check (e.g., 'preserve -> keep | additional -> more', 'never call a tab, sidebar, or section a pane'). Length comes from coverage of real rules, not padding, so it matches the 'lean and efficient; every token earns its place' anchor rather than the score-4 anchor's 'minor instances of over-explanation'.

5 / 5

Actionability

Guidance is fully concrete for an instruction-only skill: exact synonym mappings, exact panel-name capitalization lists, backtick-locking examples like '`prefers-color-scheme`', and a complete good/bad `UIStrings` code example with `@description`/`@example` tags. It does not fall to 4 because no concrete check is left as vague direction.

5 / 5

Workflow Clarity

The five sections clearly organize the review by category (do-not-flag, terminology, values, comments, consistency) and the opening scopes the trigger ('when a diff adds or modifies ... in front_end/'), but there is no explicit sequence for processing a diff (e.g., identify changed strings, then apply sections in order). It sits above the score-3 anchor (sequence present, checkpoints implicit) because this is a checklist-style single task with no destructive or batch operations requiring validation loops.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is self-contained with five clearly headed, well-scannable sections; the good/bad example sits right next to the rules it illustrates. It does not reach 5 because at ~147 lines, glossary-style content (the panel-name mapping list and synonym tables in sections 2-3) could arguably live in a reference file to keep SKILL.md a leaner overview.

4 / 5

Total

18

/

20

Passed

Description

92%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.

An exemplary description: concrete third-person capability list, explicit use/don't-use triggers with concrete artifacts (CL, diff, front_end/, i18n calls), and a sharply delimited niche. The only minor gap is a few missing natural synonyms such as 'UI text' or 'user-facing strings' among the trigger terms.

DimensionReasoningScore

Specificity

The description enumerates six concrete review actions — 'UX writing style, inline backtick locking, sentence case, UI glossary terminology, translator context, and sibling string consistency' — which is comprehensive coverage matching the 'lists multiple specific concrete actions' anchor. It stays in third person ('Reviews ...'), so no voice penalty applies.

5 / 5

Completeness

Both questions are answered explicitly: 'what' is the enumerated list of review dimensions, and 'when' is the concrete trigger 'Use when a CL or local diff adds or edits UIStrings or i18n calls in front_end/', plus an explicit negative scope ('Don't use for syntax rules already enforced by l10n ESLint rules ...'). This matches the score-5 anchor with concrete trigger phrases; the score-4 anchor's weaker/implicit 'when' does not apply.

5 / 5

Trigger Term Quality

Strong natural keyword coverage for the target user: 'UIStrings', 'localization', 'i18n calls', 'CL or local diff', 'front_end/', '@description / @example'. It sits at 4 rather than 5 because a few natural phrasings a contributor might use — 'UI text', 'user-facing strings', 'translatable strings' — are not present as triggers.

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous (Chrome DevTools UIStrings/localization review in front_end/) and the explicit 'Don't use for' clause carves out overlapping linter-enforced syntax rules, minimizing wrong-skill triggering. It clearly matches the 'clear niche with distinct triggers' anchor.

5 / 5

Total

19

/

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

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

ChromeDevTools/devtools-frontend

Path

.agents/skills/devtools-uistrings/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.