ieee-citation
Format references and in-text citations to IEEE style, and prepare Index Terms and IEEEtran bibliography setup. Use this whenever the user needs to "format…
Polish academic prose to IEEE-journal style at the sentence level — clarity, sentence length, section-appropriate tense, calibrated hedging, US English, acronym discipline, numbered-citation phrasing, and unit/number formatting. Also translate Chinese drafts into IEEE-style
$ npx -y skills add TenWalk/ieee-skills --skill ieee-polishing --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/ieee-polishingContext preview
The summary Claude sees to decide when to auto-load this skill.
Polish academic prose to IEEE-journal style at the sentence level — clarity, sentence length, section-appropriate tense, calibrated hedging, US English, acronym discipline, numbered-citation phrasing, and unit/number formatting. Also translate Chinese drafts into IEEE-style
name: ieee-polishing description: >- Polish academic prose to IEEE-journal style at the sentence level — clarity, sentence length, section-appropriate tense, calibrated hedging, US English, acronym discipline, numbered-citation phrasing, and unit/number formatting. Also translate Chinese drafts into IEEE-style English. Use this whenever the user wants to "polish", "proofread", "improve the English", "make it publishable / native", "fix the grammar", "润色", "改成地道英文", "改成投稿级" on existing text. Tuned for IEEE communications papers (per-section tense for system model / problem formulation / proposed solution / numerical results). For building or restructuring the argument and sections, use ieee-writing instead.
Use this skill to bring **existing** sentences to IEEE journal standard. If the text needs its argument or structure rebuilt, use `ieee-writing` first, then polish here.
numbers, citations, or assertions the author did not make.
verifiable clarity, not literary flair.
`optimize`, `center`, `fiber`. (This is the opposite of Nature's British spelling.)
| File | Open when | |---|---| | [references/sentence-and-style.md](references/sentence-and-style.md) | Sentence length, acronyms, articles, voice, numbers/units, US-English list, words to avoid, citation phrasing | | [references/section-moves.md](references/section-moves.md) | Choosing tense and hedging for a specific section (Abstract / Intro / Method / Results / Discussion / Conclusion) |
strong, directly measured show, demonstrate, establish inferential indicate, suggest, imply possible / partial may, can, could, appear to, is consistent with
Over-claim is the most common reviewer irritation. If the evidence is one experiment, do not say "prove" or "in all cases". Downgrade the verb instead of adding qualifiers like "very".
1. **Split into sentences.** Inspect each individually — the last sentence of a paragraph fails most. 2. **Identify the section** (it sets tense and hedging; see `references/section-moves.md`). 3. **Length and one-idea check.** Aim for ≤ ~25 words; break any sentence carrying two ideas. 4. **Tense audit.** Results = past + numbers; method-as-procedure = past; the proposed method as a standing object = present; Introduction background = present / present perfect. 5. **Edit each sentence** for subject-action clarity, articles, and US spelling. 6. **Vocabulary upgrade.** Replace vague verbs ("get", "do", "make") with precise ones; remove filler ("it is worth noting that", "as we all know", "obviously"). 7. **Acronym pass.** Define each at first use in the body; do not define in the title; avoid undefined acronyms in the abstract. 8. **Citation phrasing.** Numbered `[n]`; for author-prominent sentences use `Smith et al. [12]`, otherwise `... has been studied [12]`. Do not use `[12]` as a noun ("in [12], the authors..."). 9. **Overclaim sweep.** Flag absolutes, unwarranted causation, scope creep, and unverified "first". 10. **US-English + house style** (units, numbers, hyphenation). 11. **Proofread** for articles, plurals, agreement — the classic non-native slips. 12. **Return plain text** plus a short change log of the substantive edits.
1. `Polished:` the revised text, plain and copy-pasteable. 2. `Changes:` a short list of the *substantive* edits (not every comma) — e.g. "downgraded 'prove' → 'indicate' (one experiment)", "split a 41-word sentence", "color/behavior to US". 3. `Flags:` any sentence where wording could not be fixed without a fact the author must supply.
For Chinese input, give the polished English, then a brief 中文说明 of the main changes, and a list of any claims that need a number or citation. (See `ieee-writing`'s chinese-author-workflow.)
This repository contains two platform-adapted packages for the same IEEE communications manuscript skills.
Format references and in-text citations to IEEE style, and prepare Index Terms and IEEEtran bibliography setup. Use this whenever the user needs to "format…
Draft IEEE journal cover letters and editor-facing significance statements for new submissions or resubmissions to JSAC, TWC, TCOM, WCL, CL, and related IEEE…
Design and audit IEEE communications simulation and numerical-results sections for JSAC, TWC, TCOM, WCL, and CL. Covers benchmark schemes, Monte-Carlo…
Produce publication-grade result figures for IEEE communications papers (JSAC, TWC, TC/TCOM, WCL, CL) — correct column widths, embedded fonts, vector output…
Compile, diagnose, and fix IEEEtran LaTeX manuscripts for JSAC, TWC, TCOM, WCL, CL, and related IEEE journals: documentclass options, BibTeX/IEEEtran…
Write or compress an IEEE communications LETTER for WCL (IEEE Wireless Communications Letters) or CL (IEEE Communications Letters): a single-contribution paper…