monkilabs/panel-majority-vote
src/orchestrator/skills/panel-majority-vote/SKILL.md
Runs 3 isolated reviewer sub-agents; consolidates PASS/BLOCK verdict by majority. Use when user requests independent review of code changes, pull requests, design documents, or release notes.
$ install --global
skillsauthnpx skillsauth add monkilabs/opencastle panel-majority-voteInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 19, 2026, 7:28 AM174.8s3 files scanned
SKILL.md
- name:
- panel-majority-vote
- description:
- Runs 3 isolated reviewer sub-agents; consolidates PASS/BLOCK verdict by majority. Use when user requests independent review of code changes, pull requests, design documents, or release notes.
Skill: Panel majority vote
Inputs / Outputs
Inputs: <runRoot>, <panelKey> (filesystem-safe), question text, artifact list. Panel dir default: <runRoot>/panel/.
| File | Path |
|------|------|
| Prompt payload (optional) | <panelDir>/<panelKey>-panel-prompt.md |
| Raw reviewer outputs | <panelDir>/<panelKey>-reviewer-outputs.md |
| Consolidated report | <panelDir>/<panelKey>.md |
Procedure
-
Validate scope — every artifact path under
<runRoot>; list sufficient to answer question. -
Spawn 3 reviewers in parallel — start three isolated subagents with identical prompts. Spawn 3 reviewers using
runSubagentwith identical prompts; each reviewer receives the same question, artifact list, and constraints but runs in isolation. Required reviewer output sections (no others):VERDICT: PASS | BLOCK,MUST-FIX:,SHOULD-FIX:,QUESTIONS:,TEST IDEAS:,CONFIDENCE: low | med | high. -
Persist outputs — write
<panelDir>/<panelKey>-reviewer-outputs.mdwith a header (run root, panel key, question, artifacts) and each reviewer output verbatim, separated. -
Consolidate — parse each reviewer output for its
VERDICT:line and count PASS votes. Overall verdict = PASS if pass_count ≥ 2; otherwise BLOCK. DeduplicateMUST-FIX:andSHOULD-FIX:items and annotate each item with(N/3 reviewers).
# count PASS/BLOCK from combined outputs
pass_count=$(grep -o "VERDICT: PASS" panel/run123-reviewer-outputs.md | wc -l)
block_count=$(grep -o "VERDICT: BLOCK" panel/run123-reviewer-outputs.md | wc -l)
verdict=$([ "$pass_count" -ge 2 ] && echo PASS || echo BLOCK)
# emit a minimal JSON summary using jq (install jq if needed)
jq -n --arg panel_key "run123-panel" --arg verdict "$verdict" --argjson pass_count $pass_count --argjson block_count $block_count '{panel_key:$panel_key, verdict:$verdict, pass_count:$pass_count, block_count:$block_count}' > panel/run123-summary.json
- Write report — create
<panelDir>/<panelKey>.mdwith the minimal structure below and reference the generated summary.
- Title: Panel
<panelKey>— Verdict:PASS | BLOCK(pass_count/block_count) - Highlights: top deduplicated
MUST-FIXandSHOULD-FIXitems - Evidence: paths to reviewer outputs and
panel/run123-summary.json
-
Print summary — overall verdict + vote tally + report path.
-
Log (⛔ hard gate) — call the observability-logging skill with
panel_key,verdict,pass_count,block_count,must_fix,should_fix,reviewer_model,weighted,attempt,tracker_issue,artifacts_count,report_pathfor verification.
Notes
- On BLOCK: change underlying work; re-run; do not re-word question.
- After 3 consecutive BLOCKs on the same panel key: create a dispute record per team-lead-reference § Dispute Protocol.
- Model selection: use same model for all 3 reviewers. See team-lead-reference for model routing.
Related Resources
| Resource | Purpose |
|----------|---------|
| panel-report.template.md | Report template for step 5 |
| REFERENCE.md | Weighted consensus variant and weighting details |
| observability-logging skill | Panel logging command (step 7) |
| team-lead-reference skill | Model routing and dispute protocol |
Related Skills
monkilabs/validation-gates
development
VerifiedTrustedCommunity
Defines 10 sequential validation gates: secret scanning, lint/test/build checks, blast radius analysis, dependency auditing, browser testing, cache management, regression checks, smoke tests. Use when running pre-deploy validation or CI checks, CI/CD pipelines, deployment pipeline validation, pre-merge checks, continuous integration, or pull request validation.
44SKILL.mdUpdated Apr 21, 2026
monkilabs/testing-workflow
development
VerifiedTrustedCommunity
Generates test plans, writes unit/integration/E2E test files, identifies coverage gaps, flags common testing anti-patterns. Use when writing tests, creating test suites, planning test strategies, mocking dependencies, measuring code coverage, or test planning.
44SKILL.mdUpdated Apr 21, 2026
monkilabs/team-lead-reference
development
VerifiedTrustedCommunity
Provides model routing rules, validates delegation prerequisites, supplies cost tracking templates, defines dead-letter queue formats for Team Lead orchestration. Load when assigning tasks to agents, choosing model tiers, starting delegation session, running multi-agent workflow, delegating work, choosing which model to use, or assigning tasks.
44SKILL.mdUpdated Apr 21, 2026
monkilabs/session-checkpoints
testing
VerifiedTrustedCommunity
Saves, restores session state including task progress, file changes, delegation history. Use when saving progress, resuming interrupted work, picking up where you left off, or checkpointing current work.
44SKILL.mdUpdated Apr 21, 2026