← ClaudeAtlas

ieee-paper-drafterlisted

Draft an IEEE-conference/journal-style research paper — full section structure, IEEE numeric citation style, and a ready IEEEtran LaTeX skeleton — with the same rigor bar a reviewer would apply. Use whenever the user wants to write up a research idea, project, or result as an IEEE-format paper, or asks for an abstract/related-work/methodology section in that style. Do not use this for informal write-ups or blog-style summaries — that's plain markdown, not this skill.
hemapriyan-rk/claude-rigor-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill hemapriyan-rk/claude-rigor-skills
# IEEE Paper Drafter A paper that reads well to its author and a paper that survives peer review are different documents. The gap is almost always: omitted limitations, a related-work section that lists instead of compares, and improvement claims without a stated baseline. This skill exists to close that gap before submission, not after rejection. ## Step 1 — Use the template Copy `assets/ieee_template.tex` as the starting file (standard `IEEEtran` conference class, ready to compile). It has the full section skeleton with inline comments on what each section actually needs — follow the section order; it matches reviewer expectations and deviating from it invites confusion, not creativity points. If the user wants a `.docx` instead of LaTeX, use the `docx` skill for the file mechanics but keep the same section structure and rigor rules below. ## Step 2 — Section-by-section rigor rules - **Abstract**: self-contained, 150-250 words, no citations, includes the single strongest result as an actual number — not "significant improvement," but "X% reduction in Y." Every superlative in the abstract must be backed by a metric stated later in the paper. - **Introduction**: state the specific mechanism of failure in existing approaches, not "prior work has limitations." List contributions as explicit bullets — a reviewer scanning for contributions should not have to infer them from prose. - **Related Work**: must compare mechanisms against the nearest competing work, not just cite a