home / skills / bahayonghang / my-claude-code-settings / ieee-writing-skills

IEEE-writing-skills skill

safe

/content/skills/academic-skills/IEEE-writing-skills

This skill translates, polishes, restructures, and validates IEEE papers, ensuring strict IEEE style, academic tone, and formatting accuracy.

npx playbooks add skill bahayonghang/my-claude-code-settings --skill ieee-writing-skills

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

2.3 KB

---
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
category: academic-writing
tags: [ieee, academic, paper, translation, validation]
---

# IEEE Writing Assistant

Expert assistance for drafting, refining, and validating IEEE conference and transaction papers.

## Capabilities

1.  **Translation (CN <-> EN)**: Accurate academic translation preserving LaTeX/Typst syntax and terminology.
2.  **Polishing**: Enhancing grammar, flow, and "Academic Tone" (removing subjective/informal language).
3.  **Restructuring**: Optimizing logical flow, paragraph organization, and argument strength.
4.  **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:
1.  Run the validation script:
    ```bash
    python skills/IEEE-writing-skills/scripts/check_structure.py "path/to/paper.txt"
    ```
2.  Report issues found in the JSON output.
3.  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`.

Overview

This skill translates, polishes, restructures, and validates academic papers for IEEE conferences and transactions with strict adherence to IEEE style and academic tone. It preserves LaTeX/Typst syntax and technical terminology while enforcing formal voice and forbidden-word rules. The output targets submission-ready text compliant with IEEE formatting and editorial expectations.

How this skill works

The skill first identifies the requested task: Translate, Polish, Restructure, or Validate. For translation it preserves all LaTeX/Typst commands and technical terms while producing accurate academic English or Chinese. For polishing it tightens prose, enforces impersonal active or passive voice, and removes informal or subjective language without altering technical meaning. For restructuring it analyzes logical flow and suggests reorganization to clarify contributions and improve paragraph-level coherence. For validation it runs an automated structure and style check and reports actionable issues, including abstract length, section presence, and forbidden words.

When to use it

Preparing a manuscript for IEEE conference or journal submission.
Converting Chinese drafts to publication-quality English while preserving LaTeX/Typst code.
Improving clarity and academic tone without changing technical content.
Reorganizing a draft to make contributions and arguments explicit.
Running an automated format and style check before submission.

Best practices

Provide a clear instruction: Translate, Polish, Restructure, or Validate, and include target venue if known.
Share the source as plain text or LaTeX/Typst; keep figures and bibliographies accessible separately.
Highlight any terminology lists or preferred translations to preserve consistency.
For polishing, mark passages where technical meaning must not change.
Request a change summary or diff when you want an audit trail of edits.
When validating, allow automatic fixes for forbidden words and minor format issues.

Example use cases

Translate a Chinese LaTeX draft into IEEE-compliant English while preserving \cite{} and math notation.
Polish an abstract to 150–250 words, remove subjective language, and ensure an academic tone.
Restructure the Introduction to clearly state contributions and organize related work placement.
Validate a full manuscript for required IEEE sections, abstract length, and prohibited expressions and return a JSON report of issues.
Automatically replace forbidden words across the manuscript and produce a change log.

FAQ

Can you change technical meaning while polishing?

No. Polishing improves clarity, grammar, and tone but does not alter formulas, results, or technical claims without explicit permission.

Do you preserve LaTeX and citation commands during translation?

Yes. All LaTeX/Typst commands, citations, labels, and math environments are preserved exactly while translating surrounding text.