ieee-writer
Translate, polish, restructure, and validate academic papers for IEEE publications. Strict adherence to IEEE style, academic tone, and formatting rules.
When & Why to Use This Skill
The IEEE Writing Assistant is a specialized tool designed to streamline the creation and refinement of academic papers for IEEE conferences and journals. It ensures manuscripts meet rigorous publication standards by automating technical translation, enhancing academic tone, and performing structural validation against IEEE-specific formatting rules.
Use Cases
- Academic Translation: Converting research drafts between Chinese and English while strictly preserving LaTeX/Typst commands and technical terminology.
- Tone Refinement: Automatically removing subjective or informal language (e.g., 'amazing', 'I think') to maintain a professional, impersonal academic voice.
- Automated Validation: Running scripts to check for structural integrity, abstract word counts, and the use of forbidden words before submission.
- Structural Optimization: Reorganizing complex technical arguments and paragraph flows to improve the clarity of a paper's contribution and methodology.
| name | ieee-writer |
|---|---|
| description | Translate, polish, restructure, and validate academic papers for IEEE publications. Strict adherence to IEEE style, academic tone, and formatting rules. |
| version | 1.0 |
IEEE Writing Assistant
Expert assistance for drafting, refining, and validating IEEE conference and transaction papers.
Capabilities
- Translation (CN <-> EN): Accurate academic translation preserving LaTeX/Typst syntax and terminology.
- Polishing: Enhancing grammar, flow, and "Academic Tone" (removing subjective/informal language).
- Restructuring: Optimizing logical flow, paragraph organization, and argument strength.
- Validation: Automated checks for structure, abstract length, and forbidden words.
Instructions
1. Identify the Task
Determine if the user wants to Translate, Polish, Restructure, or Validate.
2. Apply Guidelines (Layer 2)
For ALL tasks, strictly adhere to resources/GUIDELINES.md.
- Tone Guard: Aggressively replace "very", "amazing", "I think", etc.
- Voice: Prefer impersonal active voice ("The system performs...") or passive voice over first-person ("I").
3. Execution Rules
🔤 Translation
- Maintain strict terminology consistency.
- Preserve all LaTeX commands (
\cite{},\ref{}). - Output pure text/code block, no conversational filler.
✨ Polishing
- Focus on clarity and conciseness.
- Restricted: Do NOT change the technical meaning.
- Provide a "Diff" or summary of major changes if requested.
🏗️ Restructuring
- Analyze the logical flow.
- Suggest splitting long paragraphs.
- Ensure "Introduction" covers Contribution clearly.
✅ Validation (Script)
If the user provides a file path or asks for a format check:
- Run the validation script:
python skills/IEEE-writing-skills/scripts/check_structure.py "path/to/paper.txt" - Report issues found in the JSON output.
- Offer to fix the "Forbidden Words" automatically.
Example Usage
User: "Polish this abstract."
Action: Read resources/GUIDELINES.md, check word count (mentally or via script if file), rewrite removing "very" and "good", ensure 150-250 words.
User: "Check my paper format."
Action: Run check_structure.py.