Run pprose as pprose <command> if on PATH, else uvx [email protected] <command> (zero-install via uv). Run pprose --help for every command, pprose skill for the other Practical Prose skills, and pprose list for all on-demand playbooks, style guides, and procedures (pprose shortcut, pprose guidelines, pprose runbook each print one by name).

Evaluate One Practical Prose Document

This is read-only on the source document. It writes eval report files.

Use it when the user wants a formal Practical Prose evaluation of one document.

Inputs

• Path to one Markdown artifact.
• Artifact label.
• Scope class: status, memo, brief, deep_research, or design_doc.
• ANTHROPIC_API_KEY for model scoring, unless the user asks for dry-run or manual scoring only.

Steps

1. Run pprose runbook practical-prose-eval-single for the full procedure.

2. If the artifact is a comprehensive practical guide (a reference work helping readers navigate a complex topic), read pprose guidelines writing-practical-guides for genre context before scoring; the rubric’s anchors scale with purpose, audience, genre, and risk level.

3. Generate the eval stub:

   pprose report from-metrics path/to/artifact.md --label NAME --scope-class brief --out artifact.eval.md
   

4. Inspect deterministic metrics:

   pprose metrics path/to/artifact.md --format yaml
   

5. Score the qualitative dimensions (--model is required; run pprose score --list-models for choices, or pass --dry-run to skip the API call):

   pprose score artifact.eval.md --model opus
   

6. Validate the result:

   pprose report validate artifact.eval.md --complete
   

Output

Return the eval report path, validation result, and any scoring or alignment issues that need human review.