# Praxist Diagnostic

Diagnose Praxist run health, artifact integrity, research-loop completeness...

- Repository: https://github.com/sapientinc/PRAXIST (5536 stars)
- Category: AI and agents
- License: see repository
- Last updated: 2026-09-23
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add sapientinc/PRAXIST --skill praxist-diagnostic -g -a claude-code -y`
Codex: `npx skills add sapientinc/PRAXIST --skill praxist-diagnostic -g -a codex -y`
Cursor: `npx skills add sapientinc/PRAXIST --skill praxist-diagnostic -g -a cursor -y`
Gemini CLI: `npx skills add sapientinc/PRAXIST --skill praxist-diagnostic -g -a gemini-cli -y`

## Description

Diagnose Praxist run health, artifact integrity, research-loop completeness, generation-scoped DIG/QD, PI/Gems/frontier/incubator consistency, peer memory freshness, diversity HHI, hardware utilization, LLM/runtime friction, task harness health, sustained low-performance causes, strongest variants/Pareto front, strong-variant lineage, and human-readable run reports. Use when the user asks an agent to investigate whether a current or historical Praxist run is healthy, why progress or performance is weak, whether artifacts or promotions are missing, whether guard or resource issues are blocking peers, to produce a detailed agent behavior analysis report, to generate an A/B/C run report, or to improve or optimize a task after diagnosis using task-directory-only parameter and prompt changes. Default diagnostics are analysis-only; explicit improvement mode may stop the selected run and edit task-level configuration/prompts, but must not modify Praxist core logic.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Praxist Diagnostic

Use this skill as a read-only expert diagnostic pass over an existing
Praxist task/run. The job is to determine whether the run is healthy,
whether the research loop is complete and internally consistent, whether useful
evidence is being transferred correctly, whether resources or runtime systems
are blocking progress, and whether weak performance has a process-level or
task-harness cause.

The skill is task-agnostic. Do not encode domain-specific rules, metrics,
thresholds, paths, or project names into the diagnosis. Use the task's own
`task.yaml`, evaluator outputs, manifests, logs, and documented metrics to
interpret results. If a fact is not available in artifacts, label it unknown
rather than inventing a task-specific assumption.

The rest: https://github.com/sapientinc/PRAXIST/blob/HEAD/skills/praxist-diagnostic/SKILL.md