multi-reviewer-patterns
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
73
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/agent-teams/skills/multi-reviewer-patterns/SKILL.mdQuality
Discovery
85%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 well-structured description that clearly communicates both what the skill does and when to use it. The specificity of capabilities like 'finding deduplication' and 'severity calibration' makes it distinctive. The main weakness is that trigger terms could be broader to capture more natural user phrasings like 'PR review', 'pull request review', or 'combine review feedback'.
Suggestions
Add natural trigger term variations users might say, such as 'PR review', 'pull request', 'review feedback', 'combine reviews', or 'deduplicate findings'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'coordinate parallel code reviews', 'finding deduplication', 'severity calibration', and 'consolidated reporting'. These are distinct, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting') and when ('when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'code reviews', 'severity', 'consolidated reporting', and 'multi-reviewer', but misses common natural variations users might say such as 'PR review', 'pull request', 'review feedback', 'merge duplicates', or 'review summary'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on multi-reviewer coordination, deduplication, severity calibration, and consolidated reporting creates a clear niche that is distinct from a general code review skill or a single-reviewer linting skill. Unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid reference framework for multi-reviewer code reviews with useful tables for dimension allocation, severity calibration, and a report template. Its main weaknesses are the lack of an explicit end-to-end workflow with validation checkpoints, pseudocode instead of executable examples for the deduplication process, and some verbosity in areas Claude could infer. The content is well-organized but would benefit from a clearer sequential workflow and more concrete implementation guidance.
Suggestions
Add an explicit end-to-end numbered workflow (e.g., 1. Select dimensions → 2. Run parallel reviews → 3. Deduplicate → 4. Calibrate severity → 5. Validate consistency → 6. Generate report) with validation checkpoints between steps.
Replace the pseudocode deduplication process with either executable code or more precise, unambiguous instructions that don't require interpretation.
Remove or condense the 'When to Use This Skill' section—it largely restates the skill description and adds little actionable value.
Consider splitting the report template and severity calibration tables into separate referenced files to improve progressive disclosure for this longer skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably well-structured but includes some unnecessary framing (e.g., 'When to Use This Skill' section restates what the skill does). The tables and templates are useful but could be tighter—some of the table content is somewhat obvious to Claude (e.g., what 'Security' or 'Performance' dimensions focus on). | 2 / 3 |
Actionability | The skill provides structured guidance through tables, merge rules, and a report template, which are concrete. However, the deduplication process is pseudocode rather than executable code, and there are no real code examples showing how to actually implement the coordination, deduplication, or report generation programmatically. The report template is copy-paste ready but the process steps are descriptive rather than executable. | 2 / 3 |
Workflow Clarity | The deduplication process has a clear sequence, and the overall flow (allocate dimensions → review → deduplicate → calibrate → report) is implicit but not explicitly laid out as a numbered end-to-end workflow. There are no validation checkpoints—no step to verify deduplication was done correctly or that severity calibration was applied consistently before producing the final report. | 2 / 3 |
Progressive Disclosure | The content is well-sectioned with clear headers and tables, making it easy to scan. However, it's a fairly long monolithic document (~120 lines of content) that could benefit from splitting the report template and severity calibration into referenced files. There are no cross-references to external files for deeper detail. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
91fe43e
- 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.