Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sapientinc/praxist-takeover
Orchestrate first-use Praxist onboarding, current task initialization, validation, and detached run launch from a supported agent interface.
Passed 13 of 19 test cases with the skill, and 5 of 19 without it.
and 15 more in the full report
11 fixed6 passed either way8 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.
During takeover, a new task is initialized with close-grade evidence declared. What default values must be set for `mature_supply_fraction`, `mature_supply_redundancy`, and `supply_lease_seconds`?
| Checked | Without skill | With skill |
|---|---|---|
| Sets mature_supply_fraction to 0.25. | Missed | Passed |
| Sets supply_lease_seconds to 600. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill to move a user from an existing runnable research project to a detached Praxist run in one guided flow. It composes existing skills rather than duplicating their detailed procedures:
praxist-onboarding for Praxist context and local readiness scan.praxist-task-initialization or
praxist-interactive-task-init for task-project creation.praxist-control for task validation and detached launch.The operator-facing praxist --takeover command is only a first-project
handoff into this skill. It does not replace, abbreviate, or independently
implement any step below. Treat its selected absolute project path and final
Enter confirmation as explicit operator context.
The first operational action must be the complete praxist-onboarding
workflow. Do not replace onboarding with a shorter local checklist, and do not
proceed to task initialization or launch until onboarding has produced its
readiness summary. This applies even when Codex already appears familiar with
Praxist from prior context.
When no launch-ready task exists, the next action must be the complete current
praxist-task-initialization workflow. praxist-takeover must invoke and
follow that skill rather than recreating a shortened initializer from this file. Load
and read the installed skill's current SKILL.md at execution time; do not rely
on a remembered or summarized task-init procedure. Wait for task-init's
evaluator, lane-routing regression, resource plan, and required validations to
finish before continuing. A user who invokes only praxist-takeover must
receive the same harness contract as a direct task-init user.
Print this before doing work:
**IMPORTANT PRECONDITION**
This takeover assumes the research project already runs on this machine,
with required code, data, simulator, runtime/container, and credentials present.
If those are missing, initialization must stop instead of creating a weak Praxist task.
test cases passed, vs 5 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.