ieee-polishing

ieee-polishing is a skill for Codex from CloudWave818/ieee-skills. It costs 92 tokens per session (428 once invoked), scanned A, original, MIT.

A guide for editing technical papers into the formal English style used by IEEE, a major professional and academic engineering organisation.

In plain words
What is it for?
Use it to revise abstracts, introductions, methods, results, conclusions, figure captions, rebuttals, or Chinese-to-English technical manuscripts.
Why use it?
It helps fix unclear writing, weak reasoning, unsupported claims, and wording that sounds translated or generated without changing the underlying facts.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to revise abstracts, introductions, methods, results, conclusions, figure captions, rebuttals, or Chinese-to-English technical manuscripts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cloudwave818/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 CloudWave818/ieee-skills --skill ieee-polishing
Clone the repo
git clone --depth 1 https://github.com/CloudWave818/ieee-skills

Made for: Codex.

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/cloudwave818/ieee-skills/ieee-polishing/github.svg)](https://agentmods.dev/skills/cloudwave818/ieee-skills/ieee-polishing)
Your own site
<a href="https://agentmods.dev/skills/cloudwave818/ieee-skills/ieee-polishing"><img src="https://agentmods.dev/badge/skills/cloudwave818/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/cloudwave818/ieee-skills/ieee-polishing"><img src="https://agentmods.dev/badge/skills/cloudwave818/ieee-skills/ieee-polishing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 428 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00092 $0.00428
Opus 5.5 $0.00037 $0.00171
Sonnet 5.5 $0.00018 $0.00086
Haiku 4.5 $0.00009 $0.00043

Measured 2mo ago against content hash e02ab7787ef7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

skills/ieee-polishing/SKILL.md · 43 lines

What it actually says

IEEE Polishing Router

Use this skill for IEEE-style language and logic polishing. Polishing means repairing both prose and technical argument structure.

Do not polish only from memory. Follow the routing protocol and load the selected fragments.

Routing Protocol

  1. Read manifest.yaml.
  2. Read every file listed under always_load.
  3. Detect the axes:
    • section: title / abstract / introduction / related-work / method / experiments / conclusion / caption / response / standalone.
    • language: en / zh-to-en.
    • failure_mode: vague-claims / unsupported-novelty / weak-contribution / poor-method-rationale / chinglish / result-underreporting / ai-like-prose.
    • polish_depth: light / standard / structural.
  4. State the detected axes in one short line before editing.
  5. Load only the matching fragments.
  6. Polish with this priority order:
    • preserve facts,
    • repair IEEE engineering logic,
    • align with section purpose,
    • apply failure-mode repair,
    • improve sentence-level English.

Red Lines

Do not invent numerical results, datasets, baselines, citations, equations, algorithms, or claims.

Do not hide a missing-evidence problem behind fluent English. Flag it.

Do not over-polish into Nature-style broad-interest prose. Keep IEEE direct, technical, and verifiable.

Output Contract

Default: return the polished text first, then a short Notes block only when you made structural repairs or the text still needs evidence.

For intensive editing requests, return a table with Issue | Revision | Reason.

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. 2mo ago First seen · 43 lines · 92 tokens per session scan A e02ab7787ef7

Subscribe to this mod's changes

ieee-polishing is a skill published in the GitHub repository CloudWave818/ieee-skills (429 stars, last pushed 2mo ago), licensed MIT. It adds 92 tokens to every session and 428 once invoked, about $0.0004 per session on Opus 5.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-30.

Related

ieee-polishing compared with skills from other repositories

ieee-polishing next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
ieee-polishingCloudWave818/ieee-skillsSkill4292mo agoMITA92Codex
instrument-data-to-allotropeanthropics/knowledge-work-pluginsSkill35k2d agoApache-2.0A123Claude Code
exploratory-data-analysisK-Dense-AI/scientific-agent-skillsSkill56k4d agoMITA83Claude Code
matlabK-Dense-AI/scientific-agent-skillsSkill56k4d agoMITA44Claude Code
phylogeneticsK-Dense-AI/scientific-agent-skillsSkill56k4d agoMITA71Claude Code, Codex
research-engineerdavila7/claude-code-templatesSkill33kyesterdayMITA43Claude Code, Codex
mapping-to-snomedmaziyarpanahi/openmedSkill5.8kyesterdayApache-2.0A205Claude Code