cross-modal-review

Route AI-generated outputs through a second model for review and verdict reporting.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/ltdrew/Agent-brain-2 --skill cross-modal-review-ltdrew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-modal-review
Source: https://github.com/ltdrew/Agent-brain-2/tree/main/skills/cross-modal-review
Command: npx skills add https://github.com/ltdrew/Agent-brain-2 --skill cross-modal-review-ltdrew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quality gate by requiring a second model to review work before finalization, with silent routing if a model refuses.

Core Features & Use Cases

  • Spawn a different model to review outputs, ensuring accountability and cross-checks.
  • Load and compare the originating skill's Contract to verify promised guarantees.
  • Route reviews through a chain of models and transparently report verdicts to users.
  • Handle refusals by silently switching models and escalating to the user if all fail.
  • Provide a structured Output Format that communicates reviewer, contract, verdict, and evidence.

Quick Start

Submit the produced work for cross-model review and let the system route it through the configured review chain until a verdict is delivered.

Frequently Asked Questions about cross-modal-review

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

FAQPage Schema
How do I set up a second AI model to review generated content before finalizing?

A cross-model review requires a second AI model to independently verify AI-generated outputs, analyses, and decisions before finalization. It works by loading the originating skill's contract, routing the output through a chain of models, and transparently reporting the final verdict.

How does cross-model verification handle AI refusals during the review chain?

When a model declines a review, the system employs silent refusal routing to automatically switch models within the configured chain. If all models fail, it transparently escalates the issue to the user, ensuring the quality gate is never silently bypassed.

Can I use cross-model checks to verify that an AI output meets its original contract guarantees?

Yes, cross-model checks load and compare the originating skill's Contract to verify promised guarantees. The reviewer evaluates the output against this contract and delivers a structured report detailing the reviewer, contract status, final verdict, and supporting evidence.

What is the best way to enforce a quality gate for AI-generated decisions and texts?

The best way to enforce a quality gate is requiring a second-model review before finalizing AI-generated decisions and texts. This approach applies independent verification and cross-model checks, utilizing model routing, contract loading, and grading to transparently resolve output quality.

What limitations exist when routing AI reviews through a chain of different models?

A key limitation is complete dependency on the review chain's availability; if all models in the routing chain decline the task, the system cannot provide a verdict. This constraint requires escalating the unfinished review process directly to the user.