Use when a quest needs to attach, import, reproduce, repair, verify, compare, or publish a baseline and its metrics.
This skill establishes the reference system the quest will compare against. The goal is one trustworthy comparator with a durable comparison contract, not a reproduction diary.
Follow the shared interaction contract injected by the system prompt. Keep baseline updates brief unless trust state, blocker state, route, cost, or user-facing risk changed materially.
shell_command / command_execution in this skill.bash_exec(...).artifact.git(...) before raw shell git commands.artifact.arxiv(paper_id=..., full_text=False) for actually reading a source arXiv paper when it exists.full_text=True only when the short form is insufficient.The agent owns the execution path. It may choose the workspace layout, local paths, environment manager, command order, debugging route, smoke strategy, and whether the route is attach, import, verify-local-existing, reproduce, or repair.
Do not treat templates, filenames, uv, smoke tests, detached runs, or the phase order as required paths.
They are tactics.
The hard requirement is objective evidence sufficient to accept, block, waive, or switch the baseline route.
Ask the user only when the next move depends on a real scope, cost, permission, data-access, or scientific-preference decision that cannot be inferred from the quest contract.
The baseline stage is comparator-first, not reproduction-first.
For comparison_ready, ask: