JavaScript Concept Fact Checker
leonardomso/33-js-concepts
Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.
Polish, translate, diagnose, and restructure technical manuscript text into IEEE-style academic English using routed failure-mode guidance.
Install Ieee Polishing
$ npx skills add CloudWave818/ieee-skills --skill ieee-polishing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install CloudWave818/ieee-skills ieee-polishing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/CloudWave818/ieee-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ieee-polishing .claude/skills/ieee-polishing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ieee-polishing" agent skill from https://github.com/CloudWave818/ieee-skills/tree/main/skills/ieee-polishing into .claude/skills/ieee-polishing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieee-polishing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/CloudWave818/ieee-skills/tree/main/skills/ieee-polishingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add CloudWave818/ieee-skills --skill ieee-polishing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install CloudWave818/ieee-skills ieee-polishing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CloudWave818/ieee-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ieee-polishing .agents/skills/ieee-polishing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ieee-polishing" agent skill from https://github.com/CloudWave818/ieee-skills/tree/main/skills/ieee-polishing into .agents/skills/ieee-polishing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieee-polishing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CloudWave818/ieee-skills --skill ieee-polishing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install CloudWave818/ieee-skills ieee-polishing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CloudWave818/ieee-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ieee-polishing .cursor/skills/ieee-polishing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ieee-polishing" agent skill from https://github.com/CloudWave818/ieee-skills/tree/main/skills/ieee-polishing into .cursor/skills/ieee-polishing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieee-polishing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/CloudWave818/ieee-skills.git --path skills/ieee-polishing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add CloudWave818/ieee-skills --skill ieee-polishing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install CloudWave818/ieee-skills ieee-polishing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CloudWave818/ieee-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ieee-polishing .gemini/skills/ieee-polishing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ieee-polishing" agent skill from https://github.com/CloudWave818/ieee-skills/tree/main/skills/ieee-polishing into .gemini/skills/ieee-polishing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieee-polishing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install CloudWave818/ieee-skills ieee-polishingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add CloudWave818/ieee-skills --skill ieee-polishing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/CloudWave818/ieee-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ieee-polishing .github/skills/ieee-polishing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ieee-polishing" agent skill from https://github.com/CloudWave818/ieee-skills/tree/main/skills/ieee-polishing into .github/skills/ieee-polishing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieee-polishing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CloudWave818/ieee-skills --skill ieee-polishing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install CloudWave818/ieee-skills ieee-polishing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CloudWave818/ieee-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ieee-polishing .opencode/skills/ieee-polishing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ieee-polishing" agent skill from https://github.com/CloudWave818/ieee-skills/tree/main/skills/ieee-polishing into .opencode/skills/ieee-polishing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieee-polishing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ieee-polishing- GitHub stars
- 355
- Token cost
- ~527 tokens
- SKILL.md length
- 191 words
- Files
- 30
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Polish, translate, diagnose, and restructure technical manuscript text into IEEE-style academic English using routed failure-mode guidance.
- Works in 6 steps: Read manifest.yaml. → Read every file listed under always_load. → Detect the axes → …
- Figure captions
- SKILL.md covers Routing Protocol, Red Lines and Output Contract
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ieee Polishing is an agent skill from CloudWave818/ieee-skills. Polish, translate, diagnose, and restructure technical manuscript text into IEEE-style academic English using routed failure-mode guidance. Use for IEEE abstracts, introductions, related work, methods, experiments, conclusions, figure captions, rebuttals, Chinese-to-English technical writing, AI-like or template-like academic prose, and engineering prose that needs clearer problem logic, contribution framing, method rationale, evidence discipline, natural author voice, or reviewer-ready wording.
Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. The skill folder holds 35 other files (for example `agents/openai.yaml`, `manifest.yaml` and `static/core/failure-modes.md`).
It sits in Writing & Content, covering Literature review and Technical writing. The repository describes itself as: 面向 IEEE 风格论文写作、润色、审稿、实验、图表、LaTeX、引用和论文阅读的 Codex skills。 The licence is MIT.
When your agent uses it
- Figure captions
- Chinese-to-English technical writing
- Template-like academic prose
- Engineering prose that needs clearer problem logic
Example prompts
- “/ieee-polishing”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Read manifest.yaml.
- Read every file listed under always_load.
- Detect the axes
- State the detected axes in one short line before editing.
- Load only the matching fragments.
- Polish with this priority order
What it can do on your machine
Read from SKILL.md and the folder at commit ee30fda. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ieee Polishing loads about 527 tokens when it runs. Until then it costs about 129 tokens; SKILL.md has 191 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from CloudWave818/ieee-skills at commit ee30fda, republished under its MIT licence (© CloudWave818). 191 words, ~527 tokens.
Download SKILL.mdSave it as
.claude/skills/ieee-polishing/SKILL.md (or your agent's skills folder). This skill also uses 29 other files; get the full folder from GitHub.- name
- ieee-polishing
- description
- Polish, translate, diagnose, and restructure technical manuscript text into IEEE-style academic English using routed failure-mode guidance. Use for IEEE abstracts, introductions, related work, methods, experiments, conclusions, figure captions, rebuttals, Chinese-to-English technical writing, AI-like or template-like academic prose, and engineering prose that needs clearer problem logic, contribution framing, method rationale, evidence discipline, natural author voice, or reviewer-ready wording.
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
- Read
manifest.yaml. - Read every file listed under
always_load. - 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.
- State the detected axes in one short line before editing.
- Load only the matching fragments.
- 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.
© CloudWave818, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 29 other files in skills/ieee-polishing of CloudWave818/ieee-skills.
- SKILL.md
- agents/openai.yaml
- manifest.yaml
- static/core/failure-modes.md
- static/core/output-format.md
- static/core/stance.md
- static/fragments/depth/light.md
- static/fragments/depth/standard.md
- static/fragments/depth/structural.md
- static/fragments/failure_mode/ai-like-prose.md
- static/fragments/failure_mode/chinglish.md
- static/fragments/failure_mode/poor-method-rationale.md
- static/fragments/failure_mode/result-underreporting.md
- static/fragments/failure_mode/unsupported-novelty.md
- static/fragments/failure_mode/vague-claims.md
- … and 15 more
Open the folder on GitHubat commit ee30fda
Compare with similar skills
Ieee Polishing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ieee Polishing this skillCloudWave818/ieee-skills | 355 | — | ~527 | Automated safety check: Pass | MIT | |
| JavaScript Concept Fact Checkerleonardomso/33-js-concepts | 67k | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| Beads Documentation Style Guidegastownhall/beads | 28k | — | ~3.2k | Automated safety check: Pass | MIT | |
| JavaScript Concept Page Workflowleonardomso/33-js-concepts | 67k | — | ~3.9k | Automated safety check: Pass | MIT | |
| JS Concept Resource Curatorleonardomso/33-js-concepts | 67k | — | ~4.9k | Automated safety check: Pass | MIT | |
| Technical Writing Standardcursor/plugins | 10k | 10 repos | ~2.4k | Automated safety check: Pass | None |
Similar skills
Beads Documentation Style Guide
gastownhall/beads
Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.
JavaScript Concept Page Workflow
leonardomso/33-js-concepts
Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.
JS Concept Resource Curator
leonardomso/33-js-concepts
Finds, vets, writes up and maintains external articles, videos and courses for JavaScript concept pages, including audits for broken and outdated links.
- Official
Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
Writing Docs
nukeop/nuclear
A skill your agent uses when writing or editing documentation in packages/docs.
More from CloudWave818/ieee-skills
All 10 skills in this repoIeee Figure Table
CloudWave818/ieee-skills
Audit, redesign, generate, and improve IEEE manuscript figures, tables, captions, result presentation, plotting scripts, visual polish, hybrid Python/R plus vector-editor workflows…
Ieee Summarize
CloudWave818/ieee-skills
Summarize, organize, and normalize messy research materials into an IEEE-ready writing brief before manuscript drafting.
Ieee Citation
CloudWave818/ieee-skills
Check, clean, verify, and improve IEEE citations, references, BibTeX entries, citation positioning, related-work logic, DOI metadata, venue names, and reference formatting using routed citation and…
Ieee Experiment
CloudWave818/ieee-skills
Design, audit, and strengthen experimental validation for IEEE manuscripts using routed claim-evidence checks.
Ieee Latex
CloudWave818/ieee-skills
Diagnose, fix, and improve IEEEtran LaTeX manuscripts using routed template, layout, float, equation, algorithm, table, bibliography, and PDF-compliance guidance.
Ieee Paper Reader
CloudWave818/ieee-skills
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.
Related
Categories
Questions about Ieee Polishing
What does Ieee Polishing do?
Polish, translate, diagnose, and restructure technical manuscript text into IEEE-style academic English using routed failure-mode guidance. Ieee Polishing is an agent skill from CloudWave818/ieee-skills. Polish, translate, diagnose, and restructure technical manuscript text into IEEE-style academic English using routed failure-mode guidance.
When should I use Ieee Polishing?
Ieee Polishing fits situations like: figure captions; chinese-to-English technical writing; template-like academic prose; engineering prose that needs clearer problem logic.
How do I install Ieee Polishing in Claude Code?
Run `npx skills add CloudWave818/ieee-skills --skill ieee-polishing -a claude-code`. Or copy the skill folder (skills/ieee-polishing in CloudWave818/ieee-skills) into .claude/skills/ieee-polishing in your project. Claude Code loads it when a task matches its description.
How do I install Ieee Polishing in Codex?
Run `npx skills add CloudWave818/ieee-skills --skill ieee-polishing -a codex`. Or copy the skill folder (skills/ieee-polishing in CloudWave818/ieee-skills) into .agents/skills/ieee-polishing in your project. Codex loads it when a task matches its description.
Can I use Ieee Polishing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CloudWave818/ieee-skills --skill ieee-polishing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ieee-polishing, .gemini/skills/ieee-polishing, .github/skills/ieee-polishing and .opencode/skills/ieee-polishing in your project.
What does Ieee Polishing need to run?
SKILL.md names no scripts, command-line tools or credentials: Ieee Polishing is instructions for the agent only.
Does Ieee Polishing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ieee Polishing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ieee Polishing use?
Ieee Polishing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ieee Polishing use?
About 527 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ieee Polishing?
Skills that share tags, products or a category with Ieee Polishing: JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars), Beads Documentation Style Guide (gastownhall/beads, 28k stars), JavaScript Concept Page Workflow (leonardomso/33-js-concepts, 67k stars) and JS Concept Resource Curator (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ieee Polishing?
CloudWave818 (a GitHub user) maintains it in CloudWave818/ieee-skills, which has 355 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on August 12, 2026.
Source: CloudWave818/ieee-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.