Praxist Takeover
Orchestrate first-use Praxist onboarding, current task initialization, validation, and...
Install
npx skills add sapientinc/PRAXIST --skill praxist-takeover -g -a claude-code -y- Repository
- sapientinc/PRAXIST5.5k
- Category
- AI and agents
- Updated
- 1mo ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Orchestrate first-use Praxist onboarding, current task initialization, validation, and detached run launch from a supported agent interface. Use when a user wants a one-command or one-conversation path from an existing runnable research project to a started Praxist run, asks to onboard plus initialize plus start, asks for repo-to-task-to-run setup, or wants the agent to prepare and launch Praxist with minimal interaction. This skill composes onboarding, full task initialization or task-harness repair, runtime checks, control start, and confirmation gates without changing Praxist core.
Praxist Takeover
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-onboardingfor Praxist context and local readiness scan.praxist-task-initializationorpraxist-interactive-task-initfor task-project creation.praxist-controlfor 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.
Hard Preconditions
Print this before doing work:
