critique

Orchestrates parallel multi-model critics and adjudicates disagreements into a synthesized verdict.

1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/sanjanb/my-agent-harness --skill critique-sanjanb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: critique
Source: https://github.com/sanjanb/my-agent-harness/tree/main/skills/critique
Command: npx skills add https://github.com/sanjanb/my-agent-harness --skill critique-sanjanb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-model reviews can be biased, overconfident, or miss critical issues on high-stakes outputs. This Skill dispatches independent critics from different model families, detects disagreement, and resolves conflicts through adjudication so important decisions get multi-perspective validation. ## Core Features & Use Cases - Parallel Multi-Model Panel: Dispatches three critics across different provider families (nemotron, deepseek, mimo) concurrently using background task dispatch. - Consensus & Adjudication Logic: Applies a decision table for majority verdicts, ties, and low-confidence splits, escalating to an oracle adjudicator only when critics disagree. - Domain Rubric Library: Provides structured scoring rubrics for code review, architecture, planning, and content evaluation. - Use Case: Before merging a security-sensitive code change, run the critique pipeline to collect three independent verdicts, adjudicate any split, and receive a severity-sorted findings list with a concrete recommendation. ## Quick Start Use the critique skill to run a multi-model review of this draft response and give me a synthesized verdict with combined findings.

Frequently Asked Questions about critique

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a multi-model review of an AI response?▼

Dispatch three critics in parallel using the task tool with background set to true, each routed to a different model family. Collect their verdicts, confidence scores, and findings, then apply the consensus table to produce a final synthesized verdict.

When should I use multi-critic evaluation instead of a single review?▼

Use it for high-stakes output like production code, security changes, or architecture decisions, and when single-model confidence falls below threshold. Skip it for routine edits or when a single review already has high confidence and no critical findings.

Why must critics come from different model providers?▼

Critics from the same model family share correlated biases and blind spots, making three same-family critics equivalent to one critic at triple cost. Cross-provider dispatch ensures genuinely independent perspectives.

What happens when the critics disagree with each other?▼

On a split verdict or low-confidence majority, an adjudicator receives the original request, the draft, all three critiques, and a disagreement map. It evaluates each critic's reasoning and issues a final ruling on each disputed point.

How much does a multi-model critique cost compared to a single review?▼

The three-critic panel costs roughly the same as one orchestrator review, with adjudication firing on about 30-40% of cases. Net cost is approximately 1.3-1.4 times a single review.

How do I measure whether my critic panel is working well?▼

Track Cohen's kappa for inter-rater agreement, targeting 0.6-0.8. If agreement exceeds 95% the critics are too correlated, and if adjudication exceeds 50% the rubric needs sharpening.