Cross Eval
Skill Verified Active/cs:cross-eval <memo> — Multi-model consensus on a board memo or strategy brief. Claude + Codex + Gemini cross-review with graceful degradation.
To mitigate single-model bias in high-stakes business decisions by providing a structured cross-review process across multiple AI models, ensuring a more robust and reliable outcome before irreversible commitments are made.
Features
- Multi-model consensus on business memos
- Reconciliation of LLM divergences
- Graceful degradation for model availability
- Structured output format for clarity
- Mitigation of single-model bias
Use Cases
- Before signing a term sheet
- Before announcing a layoff
- Before committing to a regulated market
- When boardroom vote was split or had critical dissent
Non-Goals
- Replacing outside counsel or a real board
- Providing definitive legal or financial advice
- Making the final decision; only surfaces points for consideration
Installation
First, add the marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install c-level-agents@claude-code-skillsQuality Score
VerifiedTrust Signals
Similar Extensions
CAIO Review
100/cs:caio-review <plan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring.
SaaS Economics Efficiency Metrics
100Evaluate SaaS unit economics and capital efficiency. Use when deciding whether the business can scale efficiently or needs correction.
Office Hours
100/cs:office-hours <topic> — YC-style 6-question founder interrogation before any advice. Forces clarity on problem, customer, distribution, defensibility, capital, and founder fit.
Prepare Inspection Readiness
100Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.
Monitor Data Integrity
100Design and operate a data integrity monitoring programme based on ALCOA+ principles. Covers detective controls, audit trail review schedules, anomaly detection patterns (off-hours activity, sequential modifications, bulk changes), metrics dashboards, investigation triggers, and escalation matrix definition. Use when establishing a data integrity monitoring programme for GxP systems, preparing for inspections where data integrity is a focus area, after a data integrity incident requiring enhanced monitoring, or when implementing MHRA, WHO, or PIC/S guidance.
Investigate Capa Root Cause
100Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.