Checklist
How Clean Language checks the result.
Note
This is the actual guidance the skill uses. This page presents the skill's quality checklist. Read the exact source, qa-checklist.md, on GitHub (opens in a new tab).
Section 1
1Accuracy
- 1.1
Did the output preserve every material fact, name, date, figure, qualification, and commitment?
- 1.2
Did the output introduce any owner, figure, date, risk, cause, or action that the source does not contain? If so, remove it or flag it as missing.
- 1.3
Did any stylistic change alter technical, legal, contractual, policy, or standards meaning?
- 1.4
Are assumptions and uncertainty labelled accurately?
- 1.5
Did the output preserve every citation, source attribution, quotation, hyperlink target, footnote, and cross-reference, and the tie between each claim and its source, with none invented?
Section 2
2Directness
- 2.1
Does the first sentence contain the answer, decision, finding, request, or purpose?
- 2.2
Can any introductory sentence be removed without loss?
- 2.3
Is the required action explicit?
- 2.4
Is an intensifier or connector such as “highly relevant” or “aligns closely with” standing in for a direct statement?
Section 3
3Ownership and consequence
- 3.1
Does the text identify who owns the action or decision when relevant?
- 3.2
Does it name the actual impact, risk, cost, dependency, or failure mode that the source supports, and flag any that the source leaves unstated rather than inventing one?
- 3.3
Does it avoid vague statements of importance?
Section 4
4Natural language
- 4.1
Does the cadence vary without becoming theatrical?
- 4.2
Are fragments, 1-line conclusions, conjunction-opened sentences, and rhetorical contrasts used sparingly?
- 4.3
Does the text sound like a competent person wrote it for this audience?
- 4.4
Could a polished phrase here appear unchanged in thousands of executive messages? Make it specific or remove it.
- 4.5
Does the message sound like the writer, not a generic executive voice?
Section 5
5Density
- 5.1
Can any word, sentence, paragraph, heading, or repetition be removed without changing meaning or creating a misreading?
- 5.2
Are bullets or tables being used because they improve comprehension rather than because they are conventional?
- 5.3
Does each paragraph do 1 identifiable job?
- 5.4
Does each topic list connect to a decision, question, or request, rather than only cataloguing subjects?
Section 6
6Tone
- 6.1
Is the language calm, exact, and appropriately blunt?
- 6.2
Did the output avoid unrequested praise, reassurance, apology, or enthusiasm?
- 6.3
Did it avoid negative-to-positive framing that weakens the finding?
Section 7
7Mechanics
- 7.1
Use the selected spelling variant consistently: Oxford English with -ize by default, or the variant the user's instructions name.
- 7.2
After any verb that can take either a direct object or a clause, such as “confirm”, “verify”, “ensure”, “note”, or “report”, check whether the following words could be read as a direct object when a clause is intended; if so, mark the clause with “that”, adding it where it is missing. The density review does not remove this “that”.
- 7.3
Follow “ensure” with “that” and a clause, never a bare noun.
- 7.4
Use numerals for quantities, measurements, versions, and dates; keep established terminology and proper names in their canonical form.
- 7.5
Remove every em and en dash, converting each to the punctuation the sentence needs; write numeric and date ranges with a hyphen or “to”. Keep a dash only inside quoted or verbatim material.
- 7.6
Use punctuation and capitalization consistently.
- 7.7
Preserve channel-specific formatting requirements.
- 7.8
Do not end with an optional offer or generic engagement prompt.