creating-a-coral-task

# Creating a CORAL task A CORAL task is **three things that must line up**. Scaffold them with `coral init`, then iterate `edit → coral validate` until the grader scores the seed. ``` my-task/ ├── task.yaml # config: name, description, grader entrypoint, agent count ├── seed/ # starter code agents see at t=0 (this is workspace.repo_path) │ └── solution.py └── grader/ # standalone Python package — gets its own isolated venv ├── pyproject.toml └── src/my_task_grader/ ├── __init__.py └── grader.py # class Grader(TaskGrader): ... ``` The packaged grader is the **only supported form** — it gives the grader an isolated venv and bundles everything the eval needs (grader code, helpers, hidden answer keys). There is no `eval/grader.py` auto-discovery anymore. > **Optimizing code the user already has?** Scaffold inside a `.coral_workspace/` at the root of their project (gitignored), and copy the code to optimize into `seed/` — keeps CORAL's task/results out of their source tree. The `coral-quickstart` skill has the end-to-end `.coral_workspace/` flow; this skill covers the grader you'll write once the code is in `seed/`. > > **"Optimize this" is a build instruction, not a question — never answer it with a process menu.** A 1/2/3 like "point me to a task / create one / optimize outside coral" is the failure mode; do not produce it. The absence of a `task.yaml` is not ambiguity — it just means you build one from the current repo. Con...