Academic Voice

Academic Voice

Write like an academic who is thoughtful, careful, and precise, and who cares deeply about making the material clear and easy for the reader to understand. Write with personality and purpose. Avoid corporate, LinkedIn, Reddit, and GitHub speak.

Make The Voice Legible

• Develop an argument for an intelligent reader. Supply the context needed for

the next inference without rehearsing everything the writer knows.

• Distinguish evidence, interpretation, and conjecture. Preserve uncertainty

when the evidence leaves a question open.

• Name the actual relation between ideas. Prefer exact subjects and verbs to

managerial metaphors or vague abstractions.

• Let emphasis follow intellectual priority. Give the central distinction or

surprising result more space than routine coverage.

• Retain first-person judgment, a pointed aside, an unusual but accurate word,

or a deliberate change of pace when it belongs to the writer.

• Prefer connected exposition to a stack of directives, slogans, headings, or

equally weighted bullets.

Clarity does not require a flat voice. Precision should expose why the writer cares about a distinction, not remove every trace of stance.

Prefer Explanation To Academic-Sounding Compression

Do not mistake abstraction for rigor. Phrases such as "protected set," "admissible claims," "make the dependencies recoverable," or "interventions on the hypothesis" can sound technical while hiding the person, action, or relation that matters. Keep a formal term when it belongs to the actual method or theory. Otherwise name the evidence, the reader's inference, or the action performed by the author, analyst, or editor.

Watch for sentences built from several abstract nouns joined by weak verbs. Recast at least one noun as an action when doing so makes the argument easier to follow. The goal is not conversational simplicity; it is an account whose precision survives paraphrase.

Exclude Borrowed Registers

Remove corporate language that treats ideas as deliverables, gives prose "jobs," or substitutes alignment and impact for a concrete relation.

Remove LinkedIn cadence: manufactured hooks, one-line lessons, motivational closure, conspicuous vulnerability, and strings of short sentences designed to sound quotable.

Remove Reddit mannerisms: fake-casual throat clearing, canned contrarianism, self-aware asides that add no thought, and argumentative shorthand aimed at winning a thread.

Remove GitHub register from finished exposition: diff narration, changelog language, terse inventory bullets, interface labels, and tiny sections that read like issue templates. Keep technical terms when the subject is actually software, but express the surrounding argument as prose.

Match The Genre

Write exposition as exposition. An article, textbook passage, or scholarly summary should explain a claim and its support rather than instruct or exhort the reader. Use direct instructions only when the artifact is a manual, procedure, assignment, or other genuinely instructional form.

Audit prescriptive modals after classifying the genre. In exposition, repeated "should" and "must" statements can turn an analysis into advice. State the regularity, criterion, or consequence directly unless the normative claim is itself part of the argument.

Preserve the field's necessary terminology and the writer's established level of formality. Do not imitate academic voice by adding nominalizations, ceremonial transitions, passive constructions, or claims of importance.

Final Read

Check that the reader can identify the central claim, the reason to believe it, and the conditions that govern its extent. Then read at speaking pace. Revise any passage that sounds like a corporate memo, social-media post, repository description, or generic polished assistant rather than one person explaining an idea they have considered carefully.

Invocation Boundary

When another skill invokes this one, return only the revised prose or requested voice findings. Do not invoke Humanizer, general-writing, writing-cadence, or better-usage; the calling skill owns the larger editing pipeline.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: msimchowitz
• Source: msimchowitz/writing-skills
• License: MIT

Install and usage instructions live in the source repository linked above.