Start with the contribution guide for task design, validation, asset publication, and maintainer promotion. For agent-assisted authoring, use the create-searchswe-task skill.
New tasks belong at task-submissions/<task-name>. Choose a descriptive name of
at most five lowercase, hyphen-separated words, such as example-search.
The task- prefix and all are reserved. One PR may add multiple tasks; record
actual authors in each package.
Validate each task with grader checks and a configured coding-model trial. Use the trajectory and evaluation results to identify and correct task-setting issues, then validate the revised setting and record the final tested version. If required API keys are missing, the authoring agent should ask the contributor to configure them locally before running the trial; see the guide for details.
Maintainers promote each reviewed package to tasks/<task-name> in the same PR,
preserving its name and original authors. Commit the pure directory move
separately from finalization changes. Use a merge commit for task contributions,
not squash or rebase merge; every submission must be promoted before merging.