CtrlK
BlogDocsLog inGet started
Tessl Logo

odyssey4me/gerrit

Submit, amend, and review Gerrit changes using git-review CLI. Use when asked to submit a patchset, download a change, rebase a change request, check CR status, or manage code reviews in Gerrit.

71

Quality

89%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, well-structured skill that provides actionable git-review commands with good progressive disclosure to reference files. Its main weaknesses are some verbosity in the authentication and examples sections (explaining things Claude already knows like SSH key generation), and a lack of explicit error handling/recovery steps in the workflows. The command reference sections are excellent and copy-paste ready.

Suggestions

Trim the Authentication section — remove SSH key generation instructions and multi-auth-method explanations that Claude already knows; keep only the Gerrit-specific config commands.

Add error recovery guidance to the Daily Workflow: what to do when 'git review' fails (e.g., merge conflicts, authentication errors, missing Change-Id), with a validate-fix-retry loop.

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some unnecessary content. The Authentication section explains SSH key generation and multiple auth methods that Claude already knows. The 'Daily Workflow' examples are somewhat verbose and repeat patterns already shown in the commands section. However, the command reference sections themselves are lean and well-structured.

2 / 3

Actionability

The skill provides fully executable, copy-paste ready commands throughout. Every section includes concrete bash commands with specific flags and arguments. The script usage, git-review commands, and configuration examples are all directly actionable with real command syntax.

3 / 3

Workflow Clarity

The Daily Workflow example shows a clear sequence with verification steps (checking that changes appear, viewing change details after amending). However, there are no explicit error recovery/feedback loops — e.g., what to do if 'git review' fails, if SSH connection fails, or if submission is rejected. For operations that modify remote state, this gap is notable.

2 / 3

Progressive Disclosure

The skill has a clear overview structure with well-signaled one-level-deep references to advanced-usage.md, troubleshooting.md, common-workflows.md, and permissions.md. The main file covers essential commands and workflows while appropriately deferring advanced topics and edge cases to reference files.

3 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly identifies its domain (Gerrit code reviews via git-review CLI), lists specific concrete actions, and includes an explicit 'Use when...' clause with natural trigger terms. The description is concise, uses third person voice, and is highly distinctive due to its Gerrit-specific terminology.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: submit, amend, review Gerrit changes, submit a patchset, download a change, rebase a change request, check CR status, manage code reviews.

3 / 3

Completeness

Clearly answers both 'what' (submit, amend, and review Gerrit changes using git-review CLI) and 'when' (explicit 'Use when...' clause listing specific trigger scenarios like submitting patchsets, downloading changes, rebasing, checking status).

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'submit a patchset', 'download a change', 'rebase', 'CR status', 'code reviews', 'Gerrit', 'git-review'. These cover common variations of how users would phrase requests.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: Gerrit-specific code review workflows using git-review CLI. The domain-specific terms (Gerrit, patchset, git-review, CR status) make it very unlikely to conflict with generic git or code review skills.

3 / 3

Total

12

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents