Academic Writing Suite

Problem

Academic writing usually stalls on section-level conventions rather than full drafting: reference styles, abstracts, keywords, introductions, methods, results, discussion, and conclusions all have different checkpoints. Sending a whole section or paper to a model without routing can mix citation formats, skip sections, or blur the logic between Discussion and Conclusion.

How It Works and Limits

• Routing: Academic Writing Suite reads the request, identifies the target section or function, and loads the matching sub-skill, such as reference-formatter/SKILL.md, abstract-writer/SKILL.md, introduction-polisher/SKILL.md, method-polisher/SKILL.md, results-polisher/SKILL.md, discussion-polisher/SKILL.md, or closing-writer/SKILL.md.
• Section handling: It separates discussion work — interpreting findings, comparing with literature, and evaluating limitations — from closing work — stating implications and recommendations. If a section combines both, it applies discussion logic first, then closing logic. A full paper is processed section by section, typically in IMRAD order.
• Reference formats: It covers APA, MLA, Chicago, IEEE, GB/T 7714, Vancouver, BibTeX, and RIS, and can handle exports related to EndNote, Zotero, or NoteExpress.
• File input: Content already in context is used directly; file reading is used when available; code execution can use python-docx, pdfplumber, or open(); otherwise the user is asked to paste the content.
• Limits: It is best for revising existing drafts, converting formats, and rewriting specific sections; if source context is missing, the user should supply it. Output defaults to English unless another language is requested.