CtrlK
BlogDocsLog inGet started
Tessl Logo

gerrit-system-logic

Provides rules, patterns, and best practices for Gerrit backend system logic, Java APIs, performance, and correctness.

46

Quality

49%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./configs/skills/gerrit_system_logic/SKILL.md
SKILL.md
Quality
Evals
Security

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 guide is a well-structured, domain-rich catalog of Gerrit backend rules with mostly executable Don't/Do Java examples, but it is severely over-long for a SKILL.md, duplicates context across executive summary, summary table, and chapter intros, and inlines everything instead of splitting chapters into reference files. Risky operations also lack explicit validation checkpoints.

Suggestions

Collapse the Executive Summary and per-chapter Context paragraphs (which duplicate the Summary table) into a single concise overview to remove hundreds of lines of repetition.

Move the 13 detailed chapter rules into per-chapter reference files under references/ (e.g. references/jgit-concurrency.md) and keep SKILL.md as a short overview with one-level-deep links, enabling progressive disclosure.

Add explicit validation/feedback steps to the destructive and batch rules (e.g. T2-01 schema rollout: 'verify readers accept both V1/V2 before enabling the V2 writer; re-validate on failure') so workflow clarity can rise above 3.

DimensionReasoningScore

Conciseness

The 2559-line body is noticeably verbose: the Executive Summary, the Summary table, and each chapter's Context paragraph restate the same material nearly verbatim, and marketing prose ('definitive reference', 'guarantees that the platform remains scalable, secure, and resilient') pads without instructing; it is above 1 because the core rules are domain-specific tribal knowledge rather than concepts Claude already knows.

2 / 5

Actionability

Most rules pair concrete 'Don't'/'Do' Java snippets (e.g. per-thread RevWalk, ConcurrentHashMap pre-allocation) that are largely copy-paste ready, matching 'mostly executable guidance with minor gaps'; it is not 5 because several 'Do' blocks are stubs (T2-02's Do is the same Gson call as the Don't with only a comment, T9-07 and T12-02 lean on prose rather than complete code).

4 / 5

Workflow Clarity

Rules are organized into a consistent Rule/What/Applies To/Why/Trap/Don't/Do sequence with cross-domain dependency pointers, but destructive or batch-prone operations (schema rollouts, cache serialization, parallel formatting) lack explicit validate-then-proceed checkpoints and feedback loops, capping the score at 3 per the destructive/batch guidance.

3 / 5

Progressive Disclosure

No bundle files exist and the body contains zero references to separate files; all 13 chapters are fully inlined into one 2559-line SKILL.md, fitting 'some structure but content that should be separate is inline'; it is above 2 because chapter/section headers and summary tables provide real navigational structure rather than a monolithic wall.

3 / 5

Total

12

/

20

Passed

Description

48%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 names a clear Gerrit-specific niche but relies on generic action verbs ('provides rules, patterns, and best practices') and omits any 'Use when...' trigger guidance. It is distinguishable from other skills yet underspecified on both concrete capabilities and activation conditions.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Enforces per-thread JGit isolation, two-step NoteDb schema rollouts, and CLA checks on Gerrit REST endpoints'.

Add an explicit trigger clause such as 'Use when modifying Gerrit backend Java code, touching NoteDb/Protobuf serialization, or changing project access REST endpoints'.

Include natural user-facing terms like 'code review', 'concurrency', 'schema migration', and 'thread safety' to improve trigger matching.

DimensionReasoningScore

Specificity

The phrase 'Provides rules, patterns, and best practices' names the Gerrit backend domain but the actions are generic categories rather than concrete operations, matching the 'names the domain but actions are minimal or generic' anchor; it does not reach 3 because no concrete actions like 'enforce two-step schema rollouts' or 'isolate JGit RevWalk per thread' are stated.

2 / 5

Completeness

It clearly states what the skill provides ('rules, patterns, and best practices for Gerrit backend system logic...') but includes no 'Use when...' clause or equivalent trigger guidance, so per the missing-trigger cap it stays at 3 rather than 4.

3 / 5

Trigger Term Quality

Terms 'Gerrit backend system logic, Java APIs, performance, and correctness' give some relevant keywords a user would say, but common variations and synonyms (e.g. 'code review', 'concurrency', 'schema migration', 'thread safety') are missing, fitting the 'some relevant keywords but missing common variations' anchor; not 4 because keyword coverage is thin rather than good.

3 / 5

Distinctiveness Conflict Risk

The Gerrit-specific scope ('Gerrit backend system logic, Java APIs') carves a clear niche with low conflict risk against non-Gerrit skills, matching 'mostly distinct; minor overlap risk'; it does not reach 5 because the broad span (logic, APIs, performance, correctness) could overlap with sibling Gerrit skills.

4 / 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (2560 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
GerritCodeReview/gerrit
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.