What problem does it solve? Delivering a skill, update, application, or file without a final check leads to real failures: incomplete deliveries (only part of the changed files handed over), lost work between sessions, eval schema drift, forgotten validations, and duplicate changelog versions. This gate runs a mandatory checklist before anything is handed to the user. ## Core Features & Use Cases - Orchestrated pre-delivery checklist: Invokes validation-mesh, safety-compliance-gate, evals verification, and skill_guard snapshot/validate without duplicating their logic. - Delivery completeness manifest: Enumerates all changed artifacts and blocks delivery until every one is included, preventing partial handoffs. - Anti-loss state protection: Requires a continuation-memory snapshot and long-term memory update before delivery to survive context compression or session interruption. - Use Case: Before handing a user an updated skill package, the gate verifies validation passes, evals exist in canonical schema (name+assertions+version), the changelog version was bumped, and the source folder with evals is delivered separately since the packager strips evals from .skill files. ## Quick Start Before giving me the finished skill update, run the full pre-delivery gate checklist and confirm every check passed.
