crew-providers

Configure and verify external model providers for QA review and design second opinions.

2|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill crew-providers-mbadali25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crew-providers
Source: https://github.com/mbadali25/useful-claude-add-ons/tree/main/plugin/crew/skills/crew-providers
Command: npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill crew-providers-mbadali25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up external AI model providers (Codex, GitHub Copilot, Gemini) for code review and design feedback involves hidden failure modes: policy gates, token precedence, model-name churn, and same-family reviewers that silently agree with the author. This Skill walks through setup, verification, and correct pinning so a QA gate never silently passes. ## Core Features & Use Cases - Provider setup and verification: Step-by-step checks for Codex CLI, GitHub Copilot CLI (three ordered gates: policy, token, real call), and Gemini (CLI or direct API), each ending in a real probe call rather than a PATH check. - Model family interlock: Enforces the rule that a reviewer must come from a different model family than the author, with role pins, alternates, and an announced claude-sonnet-5 fallback. - Cost and privacy guidance: Explains Copilot AI Credits multipliers, Gemini free-tier data training trade-offs, and local-model options (Ollama, Kimi open weights) for code that must stay on the machine. - Use Case: A team wants an independent reviewer on every diff. Use this Skill to install Codex, pin gpt-5.6-luna for QA review, confirm Copilot's org policy allows the CLI, and verify each provider with a real round-trip call before trusting the gate. ## Quick Start Ask the assistant to set up Codex as a QA reviewer and verify it with a real probe call before wiring it into the review workflow.

Frequently Asked Questions about crew-providers

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

FAQPage Schema
How do I set up GitHub Copilot CLI for code review?

Copilot CLI setup has three ordered gates: enable the CLI in org Copilot policy settings, run copilot login so it holds its own token, then make one real call and check the exit code. Only after all three pass should you pin qa.copilot.model.

How do I add a second AI model to review my code?

Install the Codex CLI or GitHub Copilot CLI, verify it with a real probe call, then pin a model from a different family than the author. A reviewer from the same model family shares the author's blind spots and the review adds nothing.

Codex vs GitHub Copilot for AI code review?

Codex is a paid, single-vendor option suited as the primary QA reviewer. Copilot is a gateway to four model families (OpenAI, Google, Microsoft, Anthropic) on one subscription, billed in AI Credits with per-model multipliers.

Why does Copilot CLI return Access denied by policy settings?

This error means either the org's Copilot CLI policy is disabled or the CLI borrowed a gh token without Copilot entitlement. Check gh api orgs/<org>/copilot/billing --jq '.cli' first; if it prints enabled, run copilot login to fix the token.

Can I use a local model for private AI code review?

Yes, Ollama can run models like qwen3-coder or the open-weight kimi-k2.7-code entirely on your machine. They are weaker than frontier models but genuinely independent, and nothing leaves the box, which suits security-sensitive reviews.

Why should the AI reviewer be a different model family than the author?

A reviewer from the same family shares the author's blind spots, so it agrees with itself and defects pass the gate unseen. The family guard runs before any model pin and strikes the authoring family from the QA walk.