with one click
pprose-eval
// Score one practical document with metrics and rubric grading; read-only on source. Use when asked to score, evaluate, grade, rubric-check, or measure quality.
// Score one practical document with metrics and rubric grading; read-only on source. Use when asked to score, evaluate, grade, rubric-check, or measure quality.
Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents. Drop-in replacement for bd/Beads with simpler architecture. Use for: tracking issues/beads with dependencies, creating bugs/features/tasks, planning specs, implementing features from specs, code reviews, committing code, creating PRs, loading coding guidelines (TypeScript, Python, TDD, golden testing, Convex, monorepo patterns), code cleanup, research briefs, architecture docs, agent handoffs, and checking out third-party library source code. Invoke when user mentions: tbd, beads, bd, shortcuts, issues, bugs, tasks, features, epics, todo, tracking, specs, planning, implementation, validation, guidelines, templates, commit, PR, pull request, code review, testing, TDD, test-driven, golden testing, snapshot testing, TypeScript, Python, Convex, monorepo, cleanup, dead code, refactor, handoff, research, architecture, labels, search, checkout library, source code review, or any workflow shortcut.
Apply the common Markdown documentation guidelines to any document; modifies the doc. The basic, universal edit tier. Use when asked to tidy, clean up, conform, fix formatting/structure, or add the footer.
Compare evaluated document versions or variants; read-only on source docs. Use when asked to compare drafts, A/B versions, quality-diff docs, or pick the best.
Copy-edit a Markdown document for language and formatting (the Expression and Form dimensions); modifies the doc. A superset of pprose-common-edit. Use when asked to copy edit, proofread, polish, tighten, rewrite, or line edit.
Full editorial pass over a practical document across all 20 Practical Prose dimensions; modifies the doc AND writes an editorial-review side document. A superset of pprose-copy-edit. Use when asked for a deep or full edit, an editorial review, a substantive edit, or a strengths-and-weaknesses review with suggested fixes.
| name | pprose-eval |
| description | Score one practical document with metrics and rubric grading; read-only on source. Use when asked to score, evaluate, grade, rubric-check, or measure quality. |
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.
For the repo’s baseline batch evals, run pprose runbook practical-prose-baseline-evals
and default to running all third-party and self-eval artifacts unless the user asks for
a subset.
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.Run pprose runbook practical-prose-eval-single for the full procedure.
Generate the eval stub:
pprose report from-metrics path/to/artifact.md --label NAME --scope-class brief --out artifact.eval.md
Inspect deterministic metrics:
pprose metrics path/to/artifact.md --format yaml
Score the qualitative dimensions:
pprose score artifact.eval.md
Validate the result:
pprose report validate artifact.eval.md --complete
Return the eval report path, validation result, and any scoring or alignment issues that need human review.