scholarly-writing-refiner skill
Polishes academic English paragraph by paragraph, reviewing grammar, word choice, voice, coherence, and sentence structure. Outputs revision suggestions alongside polished text. Triggered by phrases like 'polish this paragraph,' 'check the grammar,' 'rewrite in academic English,' or keywords like manuscript editing, SCI polishing, and journal submission editing.
Is the scholarly-writing-refiner skill safe?
Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.
No findings.
Install the scholarly-writing-refiner skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/zebbern/claude-code-guide.git /tmp/claude-code-guide mkdir -p ~/.claude/skills cp -r /tmp/claude-code-guide/skills/scholarly-writing-refiner ~/.claude/skills/scholarly-writing-refiner
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
Scholarly Writing Refiner — Academic Paper English Polishing Knowledge Base
Helps users review and polish English papers paragraph by paragraph according to international academic journal standards. Covers grammar correction, academic word choice optimization, voice normalization, coherence strengthening, sentence variety, and more. Outputs revision suggestions along with the polished text.
Quick Start
Users only need to provide:
- Text to polish: One or more paragraphs of English paper content
- Paper type (optional): Journal article / Conference paper / Thesis or dissertation / Review article
- Target journal/field (optional): e.g., Nature, IEEE, AAAI, Medicine, Computer Science, etc.
- Polishing focus (optional): Comprehensive polish / Grammar only / Word choice only / Coherence only
Example:
"Polish this Introduction for me. The target venue is NeurIPS, and I'd like the language to sound more natural with better logical flow."
1. Review Dimensions Overview
Polishing is carried out across 5 dimensions. Each dimension is rated independently with specific revision suggestions:
2. Grammar Review Rules
2.1 Common Grammar Errors Checklist
2.2 Punctuation Rules
2.3 Tense Guidelines by Paper Section
3. Word Choice Optimization Rules
3.1 Colloquial → Academic Substitution Table
3.2 Vague → Precise Expression
3.3 Reducing Redundancy
4. Voice Guidelines
4.1 Active vs. Passive Voice Selection
4.2 Common Voice Issues
4.3 Academic Person Conventions
5. Coherence and Cohesion Rules
5.1 Intra-Paragraph Signaling Words
5.2 Inter-Paragraph Transition Patterns
5.3 Common Coherence Problems
6. Sentence Structure Optimization Rules
6.1 Strategies for Sentence Variety
6.2 Sentence Structure Problems to Avoid
7. Section-Specific Polishing Guide
7.1 Abstract
- Length: 150–300 words (follow the target journal's requirements)
- Structure: Background (1–2 sentences) → Problem/Motivation (1 sentence) → Method (2–3 sentences) → Results (1–2 sentences) → Conclusion/Significance (1 sentence)
- Tense: Past tense for describing the work, present tense for conclusions
- Avoid: No citations, no abbreviations without first defining them in full, no figure or table numbers
7.2 Introduction
- Structure (classic "funnel" approach): Broad context → Specific problem → Existing methods and their limitations → Proposed method/contributions → Paper outline
- Key points: Each paragraph must have a clear topic sentence; be objective when reviewing prior work — do not disparage
- Common patterns:
- "In recent years, ... has attracted increasing attention."
- "Despite significant progress, ... remains a challenge."
- "To address this issue, we propose..."
- "The main contributions of this paper are as follows:"
7.3 Related Work
- Strategy: Organize by theme (not chronologically); within each group, arrange chronologically
- Key points: Explain how each work relates to the current paper; avoid mere listing — provide commentary
- Transitions: Connect each group with transitional sentences
- Common patterns:
- "A closely related line of work focuses on..."
- "In contrast to these approaches, our method..."
- "Building upon the work of X, we extend..."
7.4 Methods
- Principle: Reproducibility — the reader should be able to replicate the experiment from the description alone
- Structure: Problem formulation → Overall framework → Detailed module descriptions → Training/optimization details
- Key points: Define all mathematical symbols upon first appearance; describe steps in execution order
7.5 Results / Experiments
- Structure: Experimental setup → Main results → Ablation studies → Analysis/Discussion
- Key points: Describe trends in text first, then reference tables/figures; avoid repeating numbers already shown in tables or figures
- Common patterns:
- "As shown in Table X, our method outperforms..."
- "We observe a consistent improvement of X% across..."
- "The ablation study reveals that..."
7.6 Discussion
- Content: Interpret the significance of results → Compare with prior work → Limitations → Future directions
- Key points: Do not shy away from limitations; the discussion should go beyond the results themselves and explore broader implications
7.7 Conclusion
- Length: Typically one paragraph, 150–250 words
- Structure: Summarize the method → Core findings → Significance/Contributions → Future work
- Avoid: Do not introduce new information or data; do not simply repeat the Abstract
8. Polishing Output Format
For each paragraph of text provided by the user, output in the following format:
### Original
[User's original text]
### Review
| Dimension | Rating | Key Issues |
|-----------|--------|-----------|
| Grammar | ✓ Good / △ Needs improvement / ✗ Significant issues | Brief description |
| Word Choice | ✓ / △ / ✗ | Brief description |
| Voice | ✓ / △ / ✗ | Brief description |
| Coherence | ✓ / △ / ✗ | Brief description |
| Sentence Structure | ✓ / △ / ✗ | Brief description |
### Detailed Changes
1. **Original**: "..."
**Revised**: "..."
**Reason**: [Specific rationale citing the rules above]
2. ...
### Polished Version
[Complete polished paragraph]9. Domain-Specific Notes
Different disciplines have their own writing conventions. Respect field-specific norms when polishing:
10. Agent Behavior Guide
When the user submits text for polishing, follow this workflow:
- Confirm details: Paper type, target journal/conference (if any), polishing focus
- Identify the section: Determine which part of the paper the text belongs to and apply the corresponding section guidelines
- Five-dimension review: Check systematically: Grammar → Word Choice → Voice → Coherence → Sentence Structure
- Annotate sentence by sentence: Provide a reason for every change, citing the specific rule
- Output the polished version: Deliver the complete polished text
- Summarize recommendations: Highlight the main catego
More skills from zebbern/claude-code-guide
- Aacademic-paper-reviewerSimulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to \"review my paper,\" \"simulate peer review,\" or \"give my paper a peer review.
- Aactive-directory-attacksThis skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration testing.
- Capi-fuzzing-bug-bountyThis skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.
- Aapi-shape-explorerGenerate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
- Aaudit-flowInteractive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export. Use for security audits, compliance documentation, flow tracing, feature ideation, brainstorming, debugging, architecture reviews, or incident post-mortems. Triggers on audit, trace flow, document flow, security review, debug flow, brainstorm, architecture review, post-mortem, incident review.
- Aauthentication-patternsAuthentication patterns: session vs JWT vs OAuth comparison, provider selection (NextAuth, Clerk, Supabase Auth), security checklist, and common mistakes. Use when implementing auth, reviewing auth flows, or choosing auth providers.
- Aaws-penetration-testingThis skill should be used when the user asks to "pentest AWS", "test AWS security", "enumerate IAM", "exploit cloud infrastructure", "AWS privilege escalation", "S3 bucket testing", "metadata SSRF", "Lambda exploitation", or needs guidance on Amazon Web Services security assessment.
- Abroken-authenticationThis skill should be used when the user asks to "test for broken authentication vulnerabilities", "assess session management security", "perform credential stuffing tests", "evaluate password policies", "test for session fixation", or "identify authentication bypass flaws". It provides comprehensive techniques for identifying authentication and session management weaknesses in web applications.
- Cburp-suite-testingThis skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp Repeater", "analyze HTTP history", or "configure proxy for web testing". It provides comprehensive guidance for using Burp Suite's core features for web application security testing.
- AcachingCaching strategies — invalidation, TTL guidelines, cache keys, cache layers, and when not to cache. Use when implementing or reviewing caching logic.
- Achart-imageGenerate publication-quality PNG chart images from data, supporting line, bar, area, candlestick, pie, and heatmap charts. Triggers when the user asks to visualize data, create a graph, plot a time series, or generate a chart for a report, alert, or dashboard. Runs as a lightweight, headless Node.js process without a browser.
- Dcloud-penetration-testingThis skill should be used when the user asks to "perform cloud penetration testing", "assess Azure or AWS or GCP security", "enumerate cloud resources", "exploit cloud misconfigurations", "test O365 security", "extract secrets from cloud environments", or "audit cloud infrastructure". It provides comprehensive techniques for security assessment across major cloud platforms.