Praxist Run Control
Starts, stops, resumes and inspects Praxist task runs from an agent interface.
Install
npx skills add sapientinc/PRAXIST --skill praxist-control -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
Start, stop, resume, inspect status, open the independent read-only foreground TUI, detect active runs, and safely repair Praxist run lifecycle boundaries from a supported agent interface. Use when the user asks to launch a Praxist task, stop or kill a run, continue/resume an interrupted run, restart from the latest safe generation, query current run progress, open or exit a live monitor, detect or list currently running Praxist tasks in the environment, inspect generation status, view incubator/frontier/leaderboard performance, check hardware load, handle interrupted PI panel or Gems reset boundaries, inspect whether a task directory is runnable, or control Praxist lifecycle commands with `praxist start`, `praxist stop`, `praxist status`, `praxist --monitor`, `praxist resume`, or `praxist resolve`.
Praxist Control
Use this skill to operate an existing Praxist task project. It controls runs; it does not create task projects, install dependencies, edit Praxist core, or change provider credentials.
Empty Request Guard
If the user invokes this skill without naming an operation, exit without taking
an action. Ask the user to specify one of: start, stop, resume, status,
monitor, or detect-active-runs. Do not infer a default lifecycle action from
an empty prompt.
Command Surface
Verify the live CLI before acting:
praxist --help
praxist start --help
praxist stop --help
praxist status --help
praxist --monitor --help
praxist resume --help
praxist resolve --help
If praxist is not on PATH but the current directory is a Praxist source
checkout, use uv run praxist .... If neither works, refuse the lifecycle action and
tell the user to install or activate Praxist first.
Prefer JSON for machine decisions:
praxist status --json
praxist start --task-path /path/to/task --daemonize --json
praxist stop <run_id> --grace 300 --json
praxist resume <run_id-or-run-dir> --daemonize --json
Use --daemonize for start and resume from agent or CI shells, or other
sandboxed shells so the run survives the launching process.
Detect Active Runs Workflow
Use this read-only workflow when the user asks which Praxist tasks are currently running, whether the environment is idle, whether another server/session has a live run, or explicitly asks to "detect active run(s)".
-
Run:
praxist status --json
