panel-majority-vote
Runs 3 isolated reviewer sub-agents and consolidates a PASS/BLOCK verdict by majority. Use when the user requests an independent review of code changes, pull requests, design documents, or release notes.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 a strong description that clearly communicates a unique mechanism (3 isolated reviewer sub-agents with majority verdict), specifies concrete actions, and includes an explicit 'Use when' clause with natural trigger terms. It is concise, uses third person voice, and would be easily distinguishable from other skills in a large skill set.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Runs 3 isolated reviewer sub-agents', 'consolidates a PASS/BLOCK verdict by majority'. These are concrete, specific mechanisms describing what the skill does. | 3 / 3 |
Completeness | Clearly answers both 'what' (runs 3 isolated reviewer sub-agents and consolidates a PASS/BLOCK verdict by majority) and 'when' (explicit 'Use when' clause covering code changes, pull requests, design documents, or release notes). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'review', 'code changes', 'pull requests', 'design documents', 'release notes', 'independent review'. These cover common variations of review-related requests. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly distinctive with its specific mechanism (3 isolated sub-agents, majority PASS/BLOCK verdict) and the 'independent review' framing. This clearly differentiates it from a simple code review or linting skill. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%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-crafted skill that efficiently describes a multi-agent review workflow with clear sequencing, concrete executable examples, and appropriate progressive disclosure. The procedure is actionable with specific file paths, output formats, and decision logic. The hard gate at step 7 and escalation path after 3 BLOCKs demonstrate thoughtful workflow design with proper validation checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. Every section serves a purpose—no unnecessary explanations of what code review is or how sub-agents work conceptually. The bash example is targeted and the tables are compact. | 3 / 3 |
Actionability | The procedure provides concrete, executable steps: specific file paths, a working bash snippet for counting verdicts and generating JSON summaries, exact output section names required from reviewers, and clear consolidation logic (pass_count ≥ 2). The reviewer output format is precisely specified. | 3 / 3 |
Workflow Clarity | The 7-step procedure is clearly sequenced with explicit validation (step 1 validates scope, step 7 is a hard gate for logging). Error recovery is addressed via the BLOCK re-run guidance and the 3-consecutive-BLOCK dispute escalation. The consolidation logic includes a clear decision rule. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references: a Related Resources table points to the report template, REFERENCE.md for weighted consensus, observability-logging skill, and team-lead-reference skill. Content is appropriately split between this overview and referenced materials. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- monkilabs/opencastle
- Commit
18c6f2c
- 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.