Review IEEE conference, journal, Transactions, Letters, or magazine manuscripts from a technical reviewer perspective using routed IEEE review gates. Use when evaluating scope fit, novelty, validity, data, clarity, compliance, advancement, engineering significance, method soundness, experiment sufficiency, baseline fairness, figure/table quality, formatting risks, rejection risk, major revision strategy, pre-submission readiness, or the quality and specificity of reviewer comments that may be generic, careless, contradictory, or possibly AI-generated.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Use this skill to simulate a strict IEEE-style technical review. The goal is to find rejection risks and actionable fixes, not to flatter the manuscript.
Do not invent reviewer identities or editorial decisions. Review only the supplied manuscript facts and clearly mark missing materials.
manifest.yaml.always_load.venue_type: transaction / journal / letter / conference / magazine / generic.review_scope: full-manuscript / abstract-intro / method / experiments / figures-tables / rebuttal-readiness / review-comment-audit.domain: ai-ml / communications / control / signal-processing / power-energy / circuits / robotics / embedded-systems / general-engineering.strictness: quick / standard / harsh.Default output:
Review setup
- Detected axes:
- Assessment boundary:
- Central claim:
- Visible evidence:
Major rejection risks
- [severity] issue -> why it matters -> fix
Technical review
- Scope:
- Novelty:
- Validity:
- Data and experiments:
- Clarity:
- Compliance:
- Advancement:
Presentation and first impression
- Figures/tables:
- Formatting/notation:
- Writing:
Actionable revision plan
1. ...
Likely decision posture
- [bounded, non-editorial assessment]
Use Critical, Major, and Minor severity labels.
Do not claim the editor's final decision.
Do not invent experiments, results, citations, line numbers, figure contents, or reviewer biographies.
Do not turn the review into author rebuttal unless the user asks for ieee-response.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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 metadata guidance. Use when preparing IEEE manuscripts, fixing bibliography errors, verifying reference completeness, improving related work, checking whether citations support claims, or identifying missing classic/recent baselines.
中文简介正在准备中。当前显示原文说明。
Design, audit, and strengthen experimental validation for IEEE manuscripts using routed claim-evidence checks. Use when planning experiments, selecting baselines, designing ablations, choosing metrics, checking fairness, adding robustness tests, explaining results, analyzing complexity, building claim-to-evidence matrices, or responding to reviewer concerns about insufficient experiments.
中文简介正在准备中。当前显示原文说明。
Audit, redesign, generate, and improve IEEE manuscript figures, tables, captions, result presentation, plotting scripts, visual polish, hybrid Python/R plus vector-editor workflows, publication-ready matplotlib house style, and layout using routed visual-evidence checks. Use when checking or creating plot readability, axes, legends, line overlap, table structure, metric reporting, captions, grayscale accessibility, IEEE one-column/two-column layout, figure/table placement, claim-evidence mapping, reviewer first-impression risks, matplotlib/seaborn or ggplot2 figure code, SVG/PDF/TIFF/PNG export, Illustrator/Inkscape/PowerPoint/Figma finishing plans, or IEEE-style engineering evidence graphics.
中文简介正在准备中。当前显示原文说明。
Diagnose, fix, and improve IEEEtran LaTeX manuscripts using routed template, layout, float, equation, algorithm, table, bibliography, and PDF-compliance guidance. Use when fixing IEEE LaTeX compile errors, overfull boxes, float placement, two-column layout, figure sizing, tables, equations, algorithms, BibTeX, citation commands, template compliance, or final submission PDF checks.
中文简介正在准备中。当前显示原文说明。
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows. Use when extracting problem setting, object-method-condition logic, contributions, method pipeline, equations, datasets, baselines, metrics, ablations, limitations, replication details, citation role, related-work positioning, implementation notes, or reviewer-style assessment from a paper, PDF, abstract, or manuscript excerpt.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。