multi-llm-review

Orchestrates parallel multi-LLM reviews of fgcz-skills plugins and aggregates findings by agreement strength.

Updated May 28, 2026
One-click install
npx skills add https://github.com/cpanse/skills --skill multi-llm-review-cpanse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-llm-review
Source: https://github.com/cpanse/skills/tree/main/meta-skills/skills/multi-llm-review
Command: npx skills add https://github.com/cpanse/skills --skill multi-llm-review-cpanse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Reviewing skill plugins with a single LLM misses semantic issues like logic bugs, citation drift, and undocumented prerequisites that a deterministic linter cannot catch, and single-model reviews inherit that model's blind spots. ## Core Features & Use Cases - Parallel multi-model review: Spawns Claude Agent personas, Codex GPT-5.5, and Cursor Composer 2.5 against the same per-plugin prompt, then aggregates findings with per-finding agreement strength (4/4 down to 1/4). - Solo-mode fallback: When external CLIs are unavailable, falls back to three Claude personas (Security/Infrastructure, Usability/Documentation, Cross-skill Consistency) with an explicit warning about weaker same-model evidence. - Structured severity classification: Tags every finding as (a) deployment-grounded, (b) usability-grounded, or (c) preference, mapping to P0/P2 actions. - Use Case: Before merging a new plugin to the fgcz-skills marketplace, run this skill to get cross-model consensus on utility verdicts and P0 findings, then append the result to the review history index. ## Quick Start Run a multi-LLM review of the bfabric-lims plugin and aggregate the findings into a consensus report.

Frequently Asked Questions about multi-llm-review

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

FAQPage Schema
How do I run a multi-LLM review of a Claude Code skill plugin?

Run the detect_reviewers.sh script to probe available reviewer CLIs, render the per-plugin prompt template with the plugin name and path, then launch Claude, Codex, and Cursor reviewers in parallel. Aggregate their markdown outputs using the aggregation template ordered by agreement strength.

What is the difference between skill-audit and multi-llm-review?

skill-audit is a deterministic linter that catches mechanical issues cheaply and instantly. multi-llm-review is the semantic complement that catches logic bugs, citation drift, and missing prerequisites requiring domain knowledge. Run skill-audit first, then multi-llm-review.

What happens when Codex or Cursor CLI is not installed?

The workflow falls back to solo mode using three Claude Agent personas focused on security, usability, and cross-skill consistency. A warning is printed because same-model agreement is weaker evidence than cross-model agreement, and P0 fixes should be re-verified with an external reviewer.

How are findings classified and prioritized in the review?

Each finding is tagged (a) deployment-grounded, (b) usability-grounded, or (c) preference. Classes (a) and (b) are P0; (c) is P2 advisory. P0 findings are then ordered by reviewer agreement strength, with 4/4 agreement requiring immediate fixes.

How much does a multi-LLM plugin review cost and take?

A single-plugin review takes roughly 5-10 minutes and about $0.30 in Codex API spend. A full marketplace sweep of six plugins with three reviewers takes around 30 minutes and $1-3, with Cursor covered by subscription.