ieee-polishing

ieee-polishing is a skill for Claude Code from TenWalk/ieee-skills. It costs 152 tokens per session (1,073 once invoked), scanned A, original, MIT.

A skill for editing academic writing sentence by sentence to match IEEE journal style. It improves clarity, grammar, terminology, tense, citations, numbers, units, and English wording while preserving the original meaning.

In plain words
What is it for?
It is for polishing existing paper text, controlling acronyms and claim strength, fixing sentence structure, standardizing technical wording, and applying US English conventions.
Why use it?
It helps make dense technical prose easier to read without adding unsupported claims. It can also translate Chinese drafts into IEEE-style English.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ieee-skills plugin — 11 skills shipped together

Good fit It is for polishing existing paper text, controlling acronyms and claim strength, fixing sentence structure, standardizing technical wording, and applying US English conventions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tenwalk/ieee-skills/ieee-polishing
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add TenWalk/ieee-skills --skill ieee-polishing
Clone the repo
git clone --depth 1 https://github.com/TenWalk/ieee-skills

Made for: Claude Code.

Or install ieee-skills, the plugin that ships this one along with the rest of its 11 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ieee-polishing

README.md
[![agentmods](https://agentmods.dev/badge/skills/tenwalk/ieee-skills/ieee-polishing/github.svg)](https://agentmods.dev/skills/tenwalk/ieee-skills/ieee-polishing)
Your own site
<a href="https://agentmods.dev/skills/tenwalk/ieee-skills/ieee-polishing"><img src="https://agentmods.dev/badge/skills/tenwalk/ieee-skills/ieee-polishing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ieee-polishing

Your own site · 80×15
<a href="https://agentmods.dev/skills/tenwalk/ieee-skills/ieee-polishing"><img src="https://agentmods.dev/badge/skills/tenwalk/ieee-skills/ieee-polishing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 152 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,073 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00152 $0.01073
Opus 5 $0.00076 $0.00536
Sonnet 5 $0.00030 $0.00215
Haiku 4.5 $0.00015 $0.00107

Measured 12d ago against content hash 77a6e185be17, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

ieee-polishing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

ieee-skills-claude/skills/ieee-polishing/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

IEEE-Style Language Polishing

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.

Core stance

  • Preserve meaning; never add claims. Polishing changes wording, not facts. Do not introduce numbers, citations, or assertions the author did not make.
  • Clarity over elegance. A plain, precise sentence beats an ornate one. IEEE values verifiable clarity, not literary flair.
  • US English by default (IEEE house style): color, analyze, modeling, behavior, optimize, center, fiber. (This is the opposite of Nature's British spelling.)
  • Calibrate claim strength to evidence (see hedging ladder below).
  • Return plain, copy-pasteable text. Do not wrap output in commentary the user must strip out.

When to open extra files

File Open when
references/sentence-and-style.md Sentence length, acronyms, articles, voice, numbers/units, US-English list, words to avoid, citation phrasing
references/section-moves.md Choosing tense and hedging for a specific section (Abstract / Intro / Method / Results / Discussion / Conclusion)

Hedging ladder (match the verb to the evidence)

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".

Polishing workflow

  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.

Read the full file on GitHub · 76 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 76 lines · 152 tokens per session scan A 77a6e185be17

Subscribe to this mod's changes

ieee-polishing is a skill published in the GitHub repository TenWalk/ieee-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 152 tokens to every session and 1,073 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

awesome-ieee-report

Generates IEEE-format LaTeX technical reports from project requirements and codebase evidence, using academic prose, pseudocode-only explanations, BibTeX references, and IEEEtran formatting.

EnesDemir143/awesome-ieee-report · 41 tokens

literature-searcher

Search CrossRef, OpenAlex, PubMed, Semantic Scholar, and optional Scopus; deduplicate results, download open-access PDFs by DOI, classify papers, monitor new results, and analyze coverage. Use when asked to search literature, monitor a topic, download an open-access paper, classify papers, or analyze literature gaps.

Dianel555/DSkills · 72 tokens

latex-empirical-tables

Set up, format, fix, and clean up LaTeX regression and estimation tables in empirical economics or finance papers. Use when (a) creating a .tex, results.tex, main.tex, or preamble to display regression or estimation output from Python (pyfixest), Stata, or R — including any mention of estout, esttab, estauto, estwide…

kennethkhoocy/applied-micro-skills · 240 tokens

paper-writer

Medical/scientific paper writing workflow skill. Manages the full pipeline from literature search to submission-ready manuscript. Creates and manages a project directory with IMRAD-format section files, literature matrix, reference management, and quality checklists. Supports both English and Japanese papers.…

kgraph57/paper-writer-skill · 106 tokens

cite-placement

Place pre-screened literature citations into a LaTeX or Word manuscript, or restyle the citations already in one. Three modes: (1) inline placement — inline \cite{}/\citet{}/\citep{} with a compiled references.bib, for author-date journals (APA, MLA, Harvard, Chicago author-date, IEEE, Vancouver); (2) footnote…

kennethkhoocy/applied-micro-skills · 181 tokens

food-research

Run a comprehensive, multi-source literature and evidence-synthesis workflow for food & nutrition science. Use when the user wants to research a food/nutrition topic in depth, do a literature review, build an evidence brief, screen and synthesize many sources, verify citations, or scope a systematic review.…

PangenomeAI/academic-skills-food-nutrition · 154 tokens