What problem does it solve? Starting a new experimental variation normally requires manually cloning the experiment repository, creating a branch, copying the parent configuration, and registering the variation in Chronicle. This Skill automates that entire setup so researchers can go from intent to an editable, registered variation in one step. ## Core Features & Use Cases - Automated repo preparation: Mints a scoped git token, shallow-clones the experiment repo, and creates an agent-format branch. - Config scaffolding: Copies the parent variation's config.yaml as a starting point for the new variation. - Variation registration: Registers the branch as an open variation in Chronicle with a description, optional name, hypothesis, and expected outcome. - Use Case: A researcher says "start a fresh variation off variation 1 with doubled width" and receives a local clone on a new branch with the config ready to edit and the variation tracked in Chronicle. ## Quick Start Ask the agent to create a new variation of your current Chronicle experiment with a short description and hypothesis, for example: start a new variation off v1 testing whether widening attention improves eval coherence.