← ClaudeAtlas

model-validationlisted

Qualify a Genesis routing model or compare a candidate against an incumbent using the isolated qualification runner, approved references and retained billing evidence. Use for model qualification and a qualification campaign; not ordinary routing edits, generic product comparisons or a request to select a model from advertised benchmarks.
WingedGuardian/GENesis-AGI · ★ 103 · AI & Automation · score 84
Install: claude install-skill WingedGuardian/GENesis-AGI
# Model validation Read `docs/reference/qualification-runner.md` for the current supported CLI and `docs/reference/qualification-transport.md` for provider identity and receipt rules. Inspect the shipped routing alias and effective request settings; do not invent a candidate catalog or assume advertised parameter support proves provider behavior. ## Recover before recreating Reconcile the private checkpoint with actual PR merges and raw verification evidence. A stale handoff's blocked commit may already be merged. Verify exact source/input bindings before reusing prior acceptance receipts; run the specific missing checks rather than automatically repeating the entire synthetic campaign. Preserve earlier failures and source generations. Keep one private checkpoint with the chosen source commit, actual approved corpus/policy identities, fixed sample, execution plan, actual consent and remaining decisions. Keep credentials, references and raw answers off public surfaces. Do not add this external client's transcript or identifiers to Genesis session tools. ## Admit the complete study offline Use a dedicated serial process, disk-backed disposable SQLite and the shared lock/resource limits for offline acceptance. Never boot the serving runtime from a worktree. Pin source hashes and use the actual production rendering, target selection and both storage entry points. Check retained source originals and the independently restored backup required by the approval metadata. The co