Academic Paper Workshop

Problem

Academic writing often splits into separate tools for literature review, drafting, charts, review, layout, and submission. Each tool is independent, so users must know which one to call and repeatedly check whether local installations are complete. This entry point organizes 14 academic subskills into a self-checking, installable, stage-routed workflow, reducing the operational cost of scattered tools and unclear stages.

How It Works

The skill routes requests into four scenarios: first install, status check, stage routing, and incremental install. When triggered, it scans local SKILL.md files, lists installed and missing subskills, and after user confirmation installs missing ones in the order literature, writing, review, and submission. It then shows a seven-stage workflow, for example routing literature research to literature-mining, writing support to academic-writing-bank or readability-pro, and submission to submission-helper. It does not perform concrete tasks directly; it dispatches to the appropriate subskill, keeping boundaries clear.

Boundaries

The skill is for organizing and routing academic writing tools. It is not suitable for non-academic documents, and it should not be used to generate whole papers or sections, or to evade plagiarism checks. For irreversible actions such as publishing, overwriting, or external sending, it pauses and waits for human confirmation. The user remains responsible for research design, data, conclusions, and academic ethics.