gerrit-frontend-engineering

Provides guidance and best practices on Polygerrit UI development, frontend architecture, and TypeScript/JS coding standards in Gerrit.

Quality

53%

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 ./configs/skills/gerrit_frontend_engineering/SKILL.md

Quality

Content

50%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 skill is a well-structured, actionable catalog of Polygerrit frontend rules with strong Don't/Do code examples, but it is severely oversized as a single monolithic file and carries heavy redundancy from duplicated Rule/What prose and a fluffy executive summary.

Suggestions

Split the seven chapters into separate reference files (e.g. references/lit-idioms.md, references/typescript-strictness.md) and keep SKILL.md as a concise overview with one-level-deep links, scoring much higher on progressive disclosure.

Collapse the duplicated "Rule" and "What" fields into a single statement per rule and delete the marketing-style Executive Summary to recover a large token budget.

Fill in the placeholder code bodies (e.g. "// logic", "// filter logic") so the "Do" examples are fully copy-paste executable.

Dimension	Reasoning	Score
Conciseness	The ~2900-line body is noticeably verbose: the Executive Summary is marketing fluff ("Welcome to...", "born from historical refactoring efforts") and every rule duplicates near-verbatim text between its "Rule" and "What" fields, creating substantial padded redundancy without teaching Claude anything new.	2 / 5
Actionability	Each rule pairs a concrete "Don't" anti-pattern with an executable "Do" TypeScript/CSS/HTML snippet, giving mostly copy-paste-ready guidance with only minor gaps (a few examples use placeholder "// logic" bodies).	4 / 5
Workflow Clarity	This is a coding-standards reference rather than a multi-step process, so each rule is internally unambiguous, but there is no sequenced workflow or validation checkpoint guidance for applying the rules as a whole.	3 / 5
Progressive Disclosure	The document has clear chapter and rule section headers, but all seven chapters (~2900 lines) are inlined into a single monolithic SKILL.md with no one-level-deep references to separate files and no bundle files present.	3 / 5
	Total	12 / 20 Passed

Description

56%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 clearly names its Gerrit/Polygerrit frontend niche but relies on a single generic action verb and omits any explicit "Use when" trigger guidance. It is distinctive and keyword-rich yet underspecified on concrete capabilities.

Suggestions

Replace "Provides guidance and best practices" with concrete actions, e.g. "Enforces Lit state-encapsulation idioms, TypeScript strictness rules, and hermetic UI test patterns for Polygerrit components."

Add an explicit trigger clause such as "Use when writing or reviewing Polygerrit UI code, Lit web components, or Gerrit frontend TypeScript."

Include common synonyms/file markers users might say (e.g. ".ts", "LitElement", "gr-* components") to round out trigger term coverage.

Dimension	Reasoning	Score
Specificity	The only action stated is "Provides guidance and best practices" while the rest ("Polygerrit UI development, frontend architecture, and TypeScript/JS coding standards") names domains rather than concrete actions, matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	A clear "what" is present but there is no "Use when..." or equivalent trigger guidance, so per the rubric guideline a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms a Gerrit frontend engineer would say are present ("Polygerrit UI development", "frontend architecture", "TypeScript/JS coding standards", "Gerrit"), giving good keyword coverage with only minor synonyms missing, fitting the above-midpoint anchor.	4 / 5
Distinctiveness Conflict Risk	The Polygerrit/Gerrit niche makes it mostly distinct from generic skills, with only minor overlap risk against broad frontend or TypeScript standards skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (2939 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: GerritCodeReview/gerrit
Path: configs/skills/gerrit_frontend_engineering/SKILL.md
Commit: 49c7e7c

Reviewed: 4 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.