# Stem Paper Polisher

> Polish STEM manuscripts for clarity, structure, academic English, venue fit, abstract, introduction, conclusion, title, keywords, highlights, cover letter, and submission readiness. Use when users need IEEE, ACM, Elsevier, Springer, Nature-family, thesis, or arXiv style improvement without changing the scientific meaning. Trigger phrases include polish paper, academic writing, revise manuscript, improve English, abstract, introduction, conclusion, title, keywords, cover letter, submission checklist, and Chinese requests about lunwen runse.

- Skill: `xiangdong-415/stem-paper-polisher` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add xiangdong-415/stem-paper-polisher`
- Raw SKILL.md: https://api.skillmd.com/api/skills/xiangdong-415/stem-paper-polisher/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Xiangdong-415 (https://skillmd.com/u/xiangdong-415)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/xiangdong-415/stem-paper-polisher

---


# STEM Paper Polisher

## Purpose

Use this skill to improve a STEM manuscript's clarity, flow, academic tone, and submission readiness while preserving technical meaning.

## Inputs To Ask For

- Manuscript text or section.
- Target venue or style family.
- Desired edit level: light language polish, structural revision, or reviewer-oriented rewrite.
- Whether the user wants Chinese-to-English translation, English polishing, or bilingual explanation.

## Editing Principles

- Preserve meaning, equations, units, citations, and claims.
- Prefer precise technical language over ornamental prose.
- Reduce repetition and vague contribution claims.
- Keep sentence structure readable for interdisciplinary reviewers.
- Strengthen transitions and topic sentences.
- Make contribution, method, evidence, and limitation easy to find.

## Workflow

1. Diagnose the section.
   - Identify unclear thesis, missing context, weak contribution, redundant paragraphs, poor transitions, and overclaims.

2. Revise structure if needed.
   - Abstract: problem, gap, method, result, significance.
   - Introduction: background, gap, contribution, method preview, results preview, roadmap.
   - Method: problem formulation, approach, reproducibility details.
   - Results: claim-led, metric-aware, figure-connected.
   - Conclusion: findings, implications, limitations, future work.

3. Polish language.
   - Fix grammar and readability.
   - Use active voice when it improves clarity.
   - Avoid inflated phrases such as "significantly enhances" unless evidence is stated.

4. Check venue fit.
   - IEEE and ACM: concise, technical, contribution-driven.
   - Elsevier and Springer: clear narrative, structured sections, careful discussion.
   - Nature-family: broad significance, strong opening, restrained claims.
   - Thesis: more context, more explanation, explicit chapter flow.

5. Provide a revision note.
   - Explain the main changes and any scientific risks that require user confirmation.

## Output Format

Provide:

- Revised text.
- Short change summary.
- Optional sentence-level alternatives for title, abstract, or contribution statements.
- Risk notes where meaning may depend on domain facts.

## Quality Checklist

- The central contribution appears early and clearly.
- Claims match the evidence.
- Paragraphs have topic sentences and logical flow.
- Technical terms are defined before heavy use.
- The edit improves clarity without inventing results or citations.