Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sapientinc/praxist-task-initialization
Convert an existing runnable computer-based research project into a formal Praxist task project, or repair a task harness that fails task-init validation.
Passed 13 of 18 test cases with the skill, and 3 of 18 without it.
and 20 more in the full report
12 fixed4 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When enabling `evaluation.constructive_peer_mix_enabled: true` in `task.yaml`, what is the standard target ratio for constructive work?
| Checked | Without skill | With skill |
|---|---|---|
| Sets constructive_target_ratio to 0.75. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill to turn a user's existing runnable research project into a Praxist task project. The output is a new task directory selected later with praxist start --task-path ...; do not edit Praxist core or generic plugins.
Before scanning or editing, display this prominently:
**IMPORTANT PRECONDITION**
Praxist task initialization assumes:
1. You already have all source code for the research project.
2. The project already runs smoothly on this machine in some environment/container.
3. Required datasets, simulators, benchmark fixtures, or control environments are already present or reachable from this machine.
If any item is false, stop and ask the user to provide the missing path, environment, dataset, or simulator before building the task.
When praxist-takeover, praxist-takeover-codex, or the user invokes this
skill to repair an existing task that
fails a required task-init check, preserve its established scientific
objective, evaluator protocol, metric directions, baseline, and runtime
ownership. Limit edits to the task harness components responsible for the
failed contract, rerun the same validations, and avoid rebuilding unrelated
task files. Ask the user before changing scientific selection semantics that
cannot be derived unambiguously from the existing task and project evidence.
Resolve paths in this order:
Default output task path is <research_project>/praxist_task unless the user provides another output path. Do not mutate the original project except to read it and, if explicitly requested, run its documented smoke/evaluation commands.
Resolve the template root before reading or copying a scaffold. Do not assume a source checkout exists after pip installation:
test cases passed, vs 3 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.