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.
93
Does it follow best practices?
Evaluation — 92%
↑ 1.91xAgent success when using this skill
Validation for skill structure
Discovery
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 an excellent skill description that follows best practices. It uses third person voice, lists specific concrete actions, includes a comprehensive 'Use when...' clause with natural trigger terms, and targets a distinct niche (Gerrit/git-review) that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Submit, amend, and review Gerrit changes using git-review CLI' clearly describes the tool and actions. The description names specific operations like submit patchset, download change, rebase change request, and check CR status. | 3 / 3 |
Completeness | Clearly answers both what ('Submit, amend, and review Gerrit changes using git-review CLI') and when ('Use when asked to submit a patchset, download a change, rebase a change request, check CR status, or manage code reviews in Gerrit') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'patchset', 'change', 'rebase', 'CR status', 'code reviews', 'Gerrit', 'git-review'. These are the exact terms developers use when working with Gerrit-based workflows. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: Gerrit and git-review are specific tools that wouldn't overlap with generic git skills or other code review systems. The triggers are unique to Gerrit workflows (patchset, CR status, git-review). | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability and clear workflows. The progressive disclosure is excellent with appropriate separation of concerns. Minor verbosity in the authentication and prerequisites sections could be tightened, but overall the skill effectively teaches Gerrit/git-review usage with concrete, executable examples.
Suggestions
Trim the authentication section - remove the explanation of multiple authentication methods since SSH is recommended; Claude doesn't need the HTTP/HTTPS context
Condense the prerequisites and initial setup sections - the explanatory text around .gitreview file creation could be reduced to just the code block with a brief header
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanations (e.g., explaining what SSH authentication is, listing multiple authentication methods when SSH is recommended). Some sections like 'Gerrit supports multiple authentication methods' could be trimmed since Claude knows these concepts. | 2 / 3 |
Actionability | Provides fully executable commands throughout with concrete examples. All git-review commands are copy-paste ready with clear flags and options. The script usage section shows exact command syntax with real arguments. | 3 / 3 |
Workflow Clarity | The 'Daily Workflow' section provides clear step-by-step sequences with verification checkpoints (e.g., 'Verify submission', 'Verify new patchset uploaded'). Multi-step processes like submitting and amending changes include explicit validation steps using the query script. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled one-level-deep references to advanced-usage.md, common-workflows.md, and troubleshooting.md. Core content is appropriately inline while detailed topics are properly externalized. | 3 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.