Skill detail
academic-writing-refiner
Directly improves academic English, grammar, readability, and style.
Inspect before use
Automated review checks relevance, not safety or endorsement. Read the source instructions before using this skill.
SKILL.md
The saved excerpt is a snapshot from review. The external source remains the complete and most current version.
---
name: academic-writing-refiner
description: "Checklist-driven academic English polishing and Chinglish correction"
metadata:
openclaw:
emoji: "🔍"
category: "writing"
subcategory: "polish"
keywords: ["academic English grammar check", "readability improvement", "academic writing style", "Chinglish correction"]
source: "https://github.com/SYSUSELab/academic-writing-guide"
---
# Academic Writing Refiner
## Overview
Academic papers are judged not only on their scientific merit but also on the quality of their English. Grammatical errors, awkward phrasing, and non-native patterns (commonly called "Chinglish" when originating from Chinese-English interference) can distract reviewers and undermine credibility.
This skill provides a systematic checklist for identifying and correcting common academic English issues. It draws from the academic-writing-guide repository (327+ stars) maintained by SYSUSELab, which catalogs frequent mistakes observed in student and researcher manuscripts across STEM disciplines.
The approach is checklist-driven: rather than relying solely on automated tools, researchers learn to recognize error patterns and self-edit effectively. This skill is especially useful for non-native English speakers preparing manuscripts for international journals and conferences.
## Common Error Categories
### Grammar and Syntax Errors
| Error Type | Example (Wrong) | Correction |
|-----------|-----------------|------------|
| Article misuse | "We propose a novel the method" | "We propose a novel method" |
| Subject-verb disagreement | "The results shows that..." | "The results show that..." |
| Tense inconsistency | "We train the model and evaluated it" | "We trained the model and evaluated it" |
| Dangling modifier | "Using gradient descent, the loss decreased" | "Using gradient descent, we decreased the loss" |
| Run-on sentence | "The model converges fast it achieves high accuracy" | "The model converges fast and achieves high accuracy" |
### Chinglish Patterns
These are interference patterns common when translating from Chinese thought patterns into English:
1. **Topic-comment structure.** Chinese allows "As for X, Y does Z." English prefers "Y does Z to X."
- Wrong: "As for the dataset, we use ImageNet."
- Better: "We use ImageNet as our dataset."
2. **Redundant verbs.** Chinese often uses verb-verb compounds that become redundant in English.
- Wrong: "We can be able to achieve..."
- Better: "We can achieve..."
3. **Missing determiners.** Chinese has no articles, leading to dropped "the/a/an."
- Wrong: "Model achieves state-of-art result."
- Better: "The model achieves a state-of-the-art result."
4. **Overuse of "respectively."**
- Wrong: "The accuracy and F1 are 95% and 0.93 respectively."
- Better: "The accuracy is 95% and the F1 score is 0.93."
5. **"With the development of..."** This opening is overused to the point of cliche.
- Better: Lead with the specific problem or finding.
## Self-Editing Checklist
Apply this checklist before submitting any manuscript:
### Pass 1: Structure and Flow
- [ ] Each paragraph has a clear topic sentence.
- [ ] Transitions connect paragraphs logically (however, therefore, in contrast).
- [ ] No paragraph exceeds 200 words.
- [ ] Figures and tables are referenced in order.
### Pass 2: Grammar and Mechanics
- [ ] All verbs agree with their subjects.
- [ ] Tense is consistent within each section (past for Methods/Results, present for general truths).
- [ ] Every acronym is defined on first use.
- [ ] No comma splices or run-on sentences.
- [ ] Articles (a, an, the) are used correctly.
### Pass 3: Style and Conciseness
- [ ] Remove "very," "really," "quite," "basically" unless essential.
- [ ] Replace "in order to" with "to."
- [ ] Replace "a large number of" with "many" or give the exact count.
- [ ] Convert passive voice to active where possible.
- [ ] Eliminate "it is well known that" and similar filler phrases.
#Read the full source on GitHub (opens external page)