orchestrate-evaluatorlisted

Score a whole Orchestrate repository across specification, evidence, generalization, determinism, security, and release readiness — and decide whether it is moving toward the top of the leaderboard. Use at each phase gate and before submission.
NITISH-R-G/hackerrank-orchestrate-skills · ★ 3 · AI & Automation · score 71

Install: claude install-skill NITISH-R-G/hackerrank-orchestrate-skills

# Orchestrate: Orchestrate Evaluator **Evidence tier: first-hand build (August 2026).** Grounded in a completed Orchestrate submission that was audited to destruction — 48 logged defects, 9 measured-and-rejected optimisations, 17 certification scripts. Every number below was measured on that system. Nothing here claims access to HackerRank's internal scoring. ## What this answers > **If I ship this today, what evidence says I am actually better?** Not "does the code look good." ## The categories, and what a top submission looks like | Category | Check | Strong signal | |---|---|---| | **Specification** | literal conformance to every clause | 0 violations, checked against transcribed constants | | **Evidence** | cited ids exist, belong, don't self-reference | 0 hallucinated | | **Generalization** | coupling probes, hardcoded ids | 0 ids in executable code; coupling probes pass | | **Determinism** | processes × hash seeds | one hash, boundary stated | | **Security** | injection, ReDoS, traversal, malformed media | every hostile input yields a valid row | | **Multimodal** | counterfactual per modality | disabling the modality changes decisions | | **Release** | fresh clone, artifact freshness, packaging | clone runs from README alone | | **Evaluation** | output distribution sanity | no near-constant predictor | ## Scoring rules that matter **Blockers cap everything.** A score that lets fourteen passes outvote one release blocker is worse than no score. Any blocker → `DO