formal-prose-review
Skill4 starsChanged 4 months agoMITView on GitHub
Use when the user asks for sentence-level editing of technical prose while preserving its substance. Do not use for proof, notation, document-flow, or substantive review.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bib-auditSkill
- bootstrap-dispatcher-runtimeSkill
- ci-debugSkill
- cloud-filesSkill
- connect-googleSkill
- daily-planSkill
- distill-to-ruttersSkill
- email-clientSkill
- email-triageSkill
- find-handoff-candidatesSkill
- get-weatherSkill
- git-workflowSkill
- hook-makerSkill
- initialize-tddSkill
- install-launchersSkill
- latex-workshopSkill
- list-managerSkill
- llm-wakeupSkill
- loose-modeSkill
- make-tex-docstringSkill
- math-dependency-graphSkill
- milestone-loggingSkill
- node-certifySkill
- node-driftSkill
- notation-reviewSkill
- online-calendarSkill
- pdf-to-markdownSkill
- prepare-handoffSkill
- proof-auditSkill
- recurring-tasksSkill
- refactor-nodeSkill
- regenerate-blueprintsSkill
- relocate-nodesSkill
- semantic-integrationSkill
- send-feedbackSkill
- setup-interface-managerSkill
- skill-makerSkill
- technical-flow-reviewSkill
- tight-modeSkill
- tool-applicabilitySkill
- update-standardsSkill
- using-compassSkill
- wrap-upSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. About 0 are common, 21 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈21
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
When this skill is used, begin with:
- Distinctive: line 29
Do not change the mathematical substance.
- Distinctive: line 41
If a language change would alter the mathematical content, do not make it silently.
- Very specific: line 43
If the document includes a top-of-document comment block or other explicit profile information, read …
- Distinctive: line 44
If the block is malformed, incomplete, or inconsistent with the shared schema, treat the profile information as missing or unclear rather …
- Distinctive: line 45
If the document includes a suitable top-of-document comment block or other explicit profile information, use it to calibrate the prose …
- Distinctive: line 47
Do not apply journal-paper prose standards mechanically to slides, presentations, or internal notes.
- Distinctive: line 72
Prefer prose that is:
- Distinctive: line 80
Do not make the prose more elaborate just to make it sound academic.
- Distinctive: line 82
Prefer active voice when it is clearer.
- Distinctive: line 83
Do not enforce active voice mechanically if passive voice better fits the sentence focus.
- Distinctive: line 86
Do not apply generic writing advice mechanically when math or economics prose conventions support a different choice.
- Distinctive: line 94
Prefer bias-free and inclusive language when possible.
- Distinctive: line 95
Do not force awkward rewrites in the name of inclusiveness, but do flag wording that is unnecessarily exclusionary, biased, or dated.
- Distinctive: line 99
Check whether the prose matches the certainty of the content.
- Distinctive: line 107
Do not make claims stronger or weaker unless the wording itself is clearly inappropriate for the stated certainty.
- Distinctive: line 111
If the user explicitly says that a wording choice is acceptable, treat that as a binding local preference unless it creates:
- Distinctive: line 116
Do not keep re-optimizing wording the user has already approved.
- Distinctive: line 128
Keep the answer concise and diagnosis-first.
- Distinctive: line 130
When structure helps, use short headings such as:
- Distinctive: line 137
Do not force a fixed template.
- Distinctive: line 147
Only give a fuller rewrite if the user asks for it.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- BEGIN BLUEPRINT INTERFACES -->Generated from
blueprint.yaml. Do not edit this block by hand.
Used Interfaces: none
<!-- END BLUEPRINT INTERFACES -->When this skill is used, begin with:
Skill: formal-prose-review
1. Goal
Your job is to polish technical prose for a formal setting.
Focus on:
- grammar
- typos
- punctuation
- sentence-level clarity
- awkward wording
- concision
- formal professional tone
Do not change the mathematical substance. This skill is for prose polish, not proof correction, notation redesign, or document restructuring.
2. Core rule
Preserve:
- mathematical claims
- assumptions
- notation
- theorem and proof structure
- technical meaning
If a language change would alter the mathematical content, do not make it silently.
If the document includes a top-of-document comment block or other explicit profile information, read ../../references/document-standards/document-profile.md and compare the block to the shared standard.
If the block is malformed, incomplete, or inconsistent with the shared schema, treat the profile information as missing or unclear rather than trusting it blindly.
If the document includes a suitable top-of-document comment block or other explicit profile information, use it to calibrate the prose standard.
In particular, use the stated document type, audience, and purpose to judge how formal, compressed, or polished the prose should be.
Do not apply journal-paper prose standards mechanically to slides, presentations, or internal notes.
3. What to check
Check for:
- grammar and agreement errors
- tense inconsistency
- unclear pronoun reference
- faulty parallelism
- article and preposition errors
- sentence boundary problems such as run-ons or fragments
- typos and spelling errors
- punctuation problems
- awkward, tangled, or clumsy sentences
- informal, chatty, or conversational phrasing
- wordiness and filler
- inflated or vague wording
- overuse of nominalizations when a clearer verb would help
- ambiguity caused by prose rather than by mathematics
- overstatement or unnecessary hedging
- biased, exclusionary, or unnecessarily non-inclusive wording
- tone that is too casual, too emotional, or insufficiently professional
4. Style principles
Prefer prose that is:
- clear
- concise
- precise
- professional
- direct without sounding casual
Formal does not mean stiff, inflated, or ornate. Do not make the prose more elaborate just to make it sound academic.
Prefer active voice when it is clearer. Do not enforce active voice mechanically if passive voice better fits the sentence focus.
Respect field conventions. Do not apply generic writing advice mechanically when math or economics prose conventions support a different choice.
Calibrate the prose standard to the document type when that information is available. For example:
- journal papers usually require stricter formal polish
- slides and presentations may be shorter, more direct, and slightly lighter in tone
- internal notes may tolerate more compression if the purpose and audience support it
Prefer bias-free and inclusive language when possible. Do not force awkward rewrites in the name of inclusiveness, but do flag wording that is unnecessarily exclusionary, biased, or dated.
5. Claim strength
Check whether the prose matches the certainty of the content.
Be alert to:
- overclaiming
- underclaiming
- vague hedging
- opinionated or rhetorical phrasing
Do not make claims stronger or weaker unless the wording itself is clearly inappropriate for the stated certainty.
6. User pushbacks and local preferences
If the user explicitly says that a wording choice is acceptable, treat that as a binding local preference unless it creates:
- a clear grammatical error
- real ambiguity
- a conflict with the requested level of formality
Do not keep re-optimizing wording the user has already approved. Distinguish between:
- hard errors that still need fixing
- stylistic choices the user has settled
7. Output
Start with:
Mode: ExploreSkill: formal-prose-review
Keep the answer concise and diagnosis-first. Organize only when useful. When structure helps, use short headings such as:
Surface issuesTone issuesAwkward wordingMinimal editsPolished version
Do not force a fixed template.
By default:
- diagnose the issues
- propose minimal corrections
- preserve the original structure as much as possible
For short passages, it is fine to give corrected text directly. For longer passages, prefer to identify the main issues first and rewrite only as much as the user asks for.
Only give a fuller rewrite if the user asks for it.
8. What not to do
Do not:
- change notation
- change assumptions or claims
- alter proof structure
- turn stylistic cleanup into substantive revision
- make the prose more ornate in the name of formality
- force generic rules such as "always use active voice"
- ignore an explicit user preference unless it causes a real problem
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

