Draft IEEE journal cover letters and editor-facing significance statements for new submissions or resubmissions to JSAC, TWC, TCOM, WCL, CL, and related IEEE venues. Use this when the user asks for a "cover letter", "submission letter", "letter to the editor", "significance statement", "special issue fit", "投稿信", "cover letter怎么写", or wants to frame novelty, scope, ethics, suggested reviewers, conflicts, or manuscript fit. For point-by-point reviewer replies use ieee-response; for rewriting manuscript sections use ieee-writing or ieee-polishing.
Instalação
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Draft IEEE journal cover letters and editor-facing significance statements for new submissions or resubmissions to JSAC, TWC, TCOM, WCL, CL, and related IEEE venues. Use this when the user asks for a "cover letter", "submission letter", "letter to the editor", "significance statement", "special issue fit", "投稿信", "cover letter怎么写", or wants to frame novelty, scope, ethics, suggested reviewers, conflicts, or manuscript fit. For point-by-point reviewer replies use ieee-response; for rewriting manuscript sections use ieee-writing or ieee-polishing.
IEEE Cover Letter and Significance Framing
Use this skill to write the editor-facing letter that accompanies an IEEE submission. The cover
letter should help the editor see fit, novelty, evidence, and compliance quickly; it is not a second
abstract and not a reviewer response.
Core stance
Editor first. State why the manuscript belongs in the target journal or special issue, what
the technical contribution is, and why the evidence is sufficient.
Specific beats promotional. Use concrete contribution/evidence language; avoid "highly
novel", "breakthrough", and unsupported impact claims.
Do not over-disclose reviewer-response detail. For a revision, summarize the main changes and
point to the response letter; do not replay every comment.
Compliance matters. Include originality, non-duplication, conflicts, ethics/data/code
statements, and suggested/opposed reviewers only when the journal asks or the user supplies them.
No fabricated names or claims. Never invent editor names, reviewer names, manuscript IDs,
funding statements, conflicts, or data availability.