critique-clarity

Solid

Reviews markdown or plain-text prose for clarity against the Federal Plain Language Guidelines and Williams' Style: readability, passive voice, sentence length, and nominalization density. Judges sentence- and passage-level readability, not whether an argument's claim is supported or its structure holds together (critique-argument covers that). Use when the user asks for feedback, a second opinion, a red-line pass, or a quality check on a memo, PRD, proposal, or any prose document before it goes out.

AI & Automation 1 stars 0 forks Updated 4 days ago Apache-2.0

Install

View on GitHub

Quality Score: 80/100

Stars 20%
10
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# critique-clarity Reviews a markdown or plain-text prose document against two operationalized rubrics: the Federal Plain Language Guidelines (`PLAIN`, open standard) and Joseph M. Williams and Joseph Bizup's *Style: Lessons in Clarity and Grace* (`WILLIAMS`, paraphrased). Together they cover readability mechanics such as active voice, sentence length, and nominalization density, alongside judged qualities such as audience fit and passage-level cohesion, and report findings as a contract-valid run envelope. **Artifact claim.** This skill evaluates markdown or plain-text prose documents: memos, PRDs, proposals, policy explanations, and similar continuous prose. It does not evaluate HTML rendering, visual layout, non-prose structured data, or any of the other five launch skills' artifact types; a document that is mostly a UI spec, an error-message list, or an argumentative essay's structure specifically is better served by `critique-usability`, `critique-microcopy`, or `critique-argument` respectively. ## Contract Every finding this skill emits conforms to `contract/critique-contract.schema.json`. See `docs/reference/critique-contract.md` for the field contracts a schema cannot check on its own: location navigable unaided, evidence quoted or measured rather than characterized, violation naming the breach, fix actionable and specific. ## Protocol Follow these four passes in order. Do not skip ahead to severity or fixes while still sweeping. 1. **Inventory.** Map the artif...

Details

Author
product-on-purpose
Repository
product-on-purpose/critique-skills
Created
3 weeks ago
Last Updated
4 days ago
Language
Python
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

critique-argument

Reviews argumentative prose - essays, proposals, position papers, recommendation memos, strategy docs, and op-eds - against the Toulmin model of argument: whether the claim, grounds, warrant, backing, qualifier, and rebuttal are present, explicit, and actually hold together. Judges the argument's structure, not prose readability or sentence mechanics (critique-clarity covers that). Use when the user asks for a review, feedback, a second opinion, a red-line pass, a quality check, or a critique of whether an argument holds up before it goes out.

1 Updated 4 days ago
product-on-purpose
Data & Documents Solid

critique-toy

Reviews short markdown field-operations notices, memos, and similar prose documents against the toy TOY-* grammar, covering a passive-voice recast that deletes the actor, a hedging phrase stacked ahead of an otherwise direct statement, and a subheading left with no body before the next heading of equal or higher level. Use when the user asks for a review, feedback, a second opinion, a red-line pass, or a quality check on one of this fixture's worked-example documents. This is the skill template's own committed fixture, not a shipped critique-family skill, and it is never registered in library.json.

1 Updated 4 days ago
product-on-purpose
AI & Automation Solid

critique-docs

Reviews technical documentation pages and page trees written in markdown against the Diataxis framework: tutorial, how-to, reference, and explanation mode fit, plus heading structure, orphaned pages, cross-mode linking, and navigation-list length. Use when the user asks for a review, feedback, a second opinion, a red-line pass, or a quality check on a docs site, a README tree, a knowledge base, or any markdown documentation before it ships.

1 Updated 4 days ago
product-on-purpose