model-release-gate

Produce evidence-based go/no-go model release decisions from quality, fairness, and robustness audits.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill model-release-gate-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-release-gate
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/inference-testing/skills/model-release-gate
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill model-release-gate-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Promoting a model from staging to production often relies on gut feel or scattered reports. This Skill aggregates quality evals, performance benchmarks, and red-team findings, then adds explanation, fairness, and adversarial-robustness audits to produce a single evidence-backed go/no-go release decision with severity-ranked blocking items. ## Core Features & Use Cases - Explanation Report: Selects the right interpretability method (SHAP, LIME, Integrated Gradients, ALE/PDP) based on model type and compute budget, producing global and token-level attributions. - Fairness Audit: Computes SPD, DI, EOD, and AOD per protected group, runs counterfactual probes, and selects pre/in/post-processing mitigations with quantified performance cost. - Adversarial Robustness Battery: Runs FGSM, PGD, C&W, and patch attacks via ART, applies defenses like adversarial training and spatial smoothing, and plots accuracy-vs-attack-strength curves. - Use Case: Before promoting a fine-tuned LLM to production, run the gate to confirm eval thresholds passed, DI stays above 0.8, no critical red-team findings remain open, and rollback thresholds are handed to the rollout strategist. ## Quick Start Use the model-release-gate skill to evaluate whether my candidate model is ready for production promotion using the latest eval, benchmark, and red-team reports.

Frequently Asked Questions about model-release-gate

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

FAQPage Schema
How do I decide if a model is ready for production release?

Aggregate quality eval results, performance benchmarks, and red-team findings, then run explanation, fairness, and adversarial-robustness audits. The release is go only when no Critical-severity item remains open, such as unresolved red-team findings or DI below 0.8.

Which SHAP method should I use for model explanation?

Use TreeSHAP for tree-based models, KernelSHAP when you need model-agnostic fidelity and can afford the compute, and Integrated Gradients or attention inspection for transformers. Prefer ALE over PDP when features correlate.

What fairness metrics indicate disparate impact in ML models?

Disparate Impact below 0.8 (the four-fifths rule) flags unfairness, alongside Statistical Parity Difference, Equal Opportunity Difference, and Average Odds Difference. Counterfactual probes confirm whether protected attributes flip outcomes.

Can FGSM and PGD attacks evaluate a hosted LLM API?

No. Gradient-based attacks like FGSM, PGD, and C&W require white-box access to differentiable models. For hosted LLM APIs, use prompt-level adversarial tests such as injection and jailbreak suites instead.

What is the difference between empirical and certifiable robustness?

Adversarial training and defenses like spatial smoothing yield empirical robustness measured only against the evaluated attack suite, not certifiable guarantees. Never generalize one PGD result to all first-order attacks.

When should a model release be blocked versus waived?

Block on Critical issues: unresolved critical red-team findings, DI under 0.8 without mitigation, faithfulness below floor, hard SLO misses, or eval data leakage. Major issues like robustness regressions can ship only with documented owner sign-off.