As a non-native English speaker pursuing a Master's in Data Science, my writing was getting 'content is great, writing needs work' feedback on every paper. I set up OpenClaw as a writing coach that understands academic conventions β and my grades jumped from B+ to A/A-.
The Writing Barrier
Strong technical skills but ESL writing patterns: awkward phrasing, inconsistent tense, weak transitions, and over-reliance on passive voice. Grammarly caught typos but missed academic style issues.
Configuration
# IDENTITY.md for Academic Writing Coach You are an academic writing coach specializing in data science and computer science papers. Your student is a non-native English speaker (L1: Korean) pursuing a Master's degree. ## Coaching Style - Point out issues AND explain WHY they're issues - Provide 2-3 alternative phrasings for each correction - Never rewrite entire paragraphs β coach, don't ghostwrite - Focus on: transitions, tense consistency, hedging language, topic sentences, and academic register ## Common Patterns to Watch For 1. Direct translations from Korean (word order issues) 2. Missing articles (a/an/the) β most common ESL error 3. Overuse of "we can see that..." and "it is shown that..." 4. Passive voice overuse (convert 50% to active) 5. Weak transitions between paragraphs 6. Inconsistent verb tense within sections ## Academic Conventions by Section - Abstract: Past tense for methods/results, present for conclusions - Introduction: Present tense for established facts, past for citations - Methods: Past tense throughout - Results: Past tense for observations, present for figures - Discussion: Mix of tenses, hedging language essential ## Feedback Format For each issue, provide: [LINE X] ISSUE: Description BEFORE: "original text" AFTER (option 1): "corrected text" AFTER (option 2): "alternative correction" WHY: Brief explanation of the rule
1. Paragraph-Level Feedback
I paste a draft paragraph and OpenClaw returns structured coaching feedback β not just corrections, but explanations of why each change matters.
Input paragraph:
"In this paper, we can see that the random forest algorithm
is performing better than the SVM. The accuracy is 94.2%
which is higher. We will discuss the results."
Coach Feedback:
[LINE 1] REGISTER: "we can see that" is informal
BEFORE: "we can see that the random forest algorithm"
AFTER: "the random forest algorithm demonstrates"
WHY: Academic writing prefers direct statements over
"we can see" constructions.
[LINE 2] TENSE: Inconsistent β use past for results
BEFORE: "is performing better"
AFTER: "outperformed"
WHY: Results section uses past tense for completed experiments.
[LINE 2] PRECISION: "higher" is vague
BEFORE: "which is higher"
AFTER: "representing a 3.7% improvement over SVM (90.5%)"
WHY: Always quantify comparisons in academic writing.
[LINE 3] HEDGING: Too definitive for upcoming discussion
BEFORE: "We will discuss"
AFTER: "These results are further examined in Section 4"
WHY: Forward references use present tense in academic convention.
Revised paragraph:
"The random forest algorithm outperformed SVM, achieving an
accuracy of 94.2% β a 3.7% improvement over SVM (90.5%).
These results are further examined in Section 4."2. Paper Structure Analysis
OpenClaw reviews the overall structure of my paper, checking section flow, argument coherence, and whether my thesis is supported by evidence.
Command: "Review the structure of my ML fairness paper" Structure Analysis: βββ Paper Flow Check βββ β Abstract (230 words) β good length, covers all elements β οΈ Introduction β thesis statement appears in paragraph 4 SUGGESTION: Move thesis to end of paragraph 2 for clarity β Related Work β covers 3 key areas β οΈ Gap: No mention of EU AI Act implications SUGGESTION: Add 1 paragraph on regulatory context β Methodology β clear, reproducible steps β Results β figures well-referenced, tables consistent β οΈ Discussion β jumps to limitations too quickly SUGGESTION: Add 2 paragraphs interpreting key findings before the limitations subsection β Conclusion β appropriately scoped, future work included Overall: B+ structure β A- with suggested changes Estimated revision time: 2-3 hours
3. Citation Integration Coaching
Teaches how to weave citations into narrative instead of just listing them β the difference between undergraduate and graduate-level writing.
BEFORE (undergraduate style): "Machine learning fairness is important. Smith (2023) studied bias. Jones (2024) proposed a framework. Lee (2023) found problems with existing approaches." Coach Feedback: This reads as a list, not a narrative. Citations should support your argument, not BE your argument. AFTER (graduate style): "The growing deployment of ML systems in high-stakes domains has intensified scrutiny of algorithmic fairness (Smith, 2023). While early frameworks attempted to formalize fairness through statistical parity (Jones, 2024), recent work has revealed fundamental tensions between competing fairness definitions (Lee, 2023), suggesting that context-specific approaches may be more appropriate than universal metrics." KEY PRINCIPLE: Each sentence should make YOUR point, with citations supporting it β not the other way around.
4. Pre-Submission Checklist
Before submitting, OpenClaw runs a comprehensive checklist covering formatting, style, academic conventions, and common deductions.
Pre-Submission Check for: ML_Fairness_Paper_v3.docx
Format Compliance:
β
IEEE double-column format
β
Font: Times New Roman 10pt
β
References: IEEE style, 28 entries
β οΈ Page count: 9 pages (limit: 8)
β Suggestion: Condense Related Work by 0.5 pages
Writing Quality:
β
Tense consistency: 94% (threshold: 90%)
β
Passive voice: 35% (target: 30-40%)
β οΈ Hedging language: Missing in 3 claims
β Lines 142, 267, 301 need "suggests" or "indicates"
β
Transition words: present in 87% of paragraph openings
β
No first-person outside Introduction/Conclusion
Citation Check:
β
All 28 references cited in text
β
No orphan citations
β οΈ 2 self-citations (under 10% threshold β OK)
β οΈ Oldest reference: 2018 β consider newer alternatives
Readability Score: Graduate Level (Flesch-Kincaid: 14.2)
Estimated Grade Impact: B+ β A-Results Over One Semester
| Metric | Before | After | Change |
|---|---|---|---|
| Average paper grade | B+ | A/A- | β 1 grade |
| ESL issues per page | 5-8 | 1-2 | β 75% |
| Revision cycles | 3-4 | 1-2 | β 50% |
| Writing time per paper | 12-15 hours | 8-10 hours | β 33% |
| Professor comments on writing | Frequent | Rare | β ~80% |
| Confidence in writing | Low | High | Qualitative β |
"My professor said 'your writing has improved dramatically this semester.' I didn't tell her about my AI coach. But I genuinely learned β I now catch most issues before even pasting into OpenClaw." β u/DataScienceKorea
Cost
| Item | Cost | Notes |
|---|---|---|
| Laptop (existing MacBook) | $0 | Runs Ollama locally |
| Ollama + Mistral-7B | $0 | Sufficient for English coaching |
| Total | $0/mo | vs $30/mo Grammarly Premium + tutor $60/hr |
Saved ~$720/semester vs. a writing tutor (12 sessions Γ $60). More importantly, the feedback is available 24/7 β not just during office hours.
FAQ
Q1. Isn't this just Grammarly?
Q2. Does it work for non-STEM papers?
Q3. Will professors detect AI-assisted writing?
Q4. What model works best for writing coaching?
Lessons Learned
Explaining WHY > just fixing
Having OpenClaw explain the rule behind each correction taught me patterns. After 2 months, I caught 60% of my own errors before pasting into the tool.
Section-specific rules matter
Academic writing isn't one style β it's different conventions per section. Configuring IDENTITY.md with section-specific tense rules was the biggest accuracy boost.
Don't fix everything at once
I focused on one issue type per week: Week 1 = articles, Week 2 = transitions, Week 3 = tense. This spaced learning approach stuck better than fixing everything simultaneously.
Keep a personal error log
I track my most common mistakes in a Notion page. After 4 months, my 'article errors' dropped from 4/page to 0.5/page. The error log is more valuable than the tool itself.