What problem does it solve? Maintaining Gemini runtime harness assets (instructions, state, verification, scope, lifecycle, validation, benchmarks) is error-prone: changes can blur owner layers, overstate verification claims, or mirror autonomous/Codex assets into the wrong location. This Skill provides a disciplined procedure for creating or adapting those assets while enforcing claim boundaries and static validation. ## Core Features & Use Cases - Structured Change Procedure: Follows an Analyze -> Plan -> Create/Revise -> Test -> Verify -> Report workflow for every harness asset change. - Owner-Layer Routing: Routes changes to the correct layer (Gemini runtime, shared state, verification, lifecycle, evidence, archive, or report) using a detailed reference guide. - Claim Boundary Enforcement: Prevents unsupported claims such as provider_verified, release_gated, or production_ready unless separately executed provider evidence exists. - Use Case: When adding a new Gemini CLI layout validation fixture, activate this Skill to place the asset under the correct owner layer, run static validation, and report the claim boundary and remaining provider risk. ## Quick Start Use the harness-creator-adapter skill to add a Gemini runtime validation fixture for the CLI layout and report the validation result and claim boundary.
