Academic Research Pipeline
Imbad0202/academic-research-skills
Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.
Core skill for the deep research and writing tool. An agent skill from LigphiDonk/Oh-my--paper.
$ npx skills add LigphiDonk/Oh-my--paper --skill scientific-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LigphiDonk/Oh-my--paper scientific-writing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LigphiDonk/Oh-my--paper.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scientific-writing .claude/skills/scientific-writing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "scientific-writing" agent skill from https://github.com/LigphiDonk/Oh-my--paper/tree/main/skills/scientific-writing into .claude/skills/scientific-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scientific-writing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LigphiDonk/Oh-my--paper/tree/main/skills/scientific-writingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LigphiDonk/Oh-my--paper --skill scientific-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LigphiDonk/Oh-my--paper scientific-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LigphiDonk/Oh-my--paper.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/scientific-writing .agents/skills/scientific-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "scientific-writing" agent skill from https://github.com/LigphiDonk/Oh-my--paper/tree/main/skills/scientific-writing into .agents/skills/scientific-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scientific-writing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LigphiDonk/Oh-my--paper --skill scientific-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LigphiDonk/Oh-my--paper scientific-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LigphiDonk/Oh-my--paper.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/scientific-writing .cursor/skills/scientific-writing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "scientific-writing" agent skill from https://github.com/LigphiDonk/Oh-my--paper/tree/main/skills/scientific-writing into .cursor/skills/scientific-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scientific-writing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LigphiDonk/Oh-my--paper.git --path skills/scientific-writing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LigphiDonk/Oh-my--paper --skill scientific-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LigphiDonk/Oh-my--paper scientific-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LigphiDonk/Oh-my--paper.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/scientific-writing .gemini/skills/scientific-writing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "scientific-writing" agent skill from https://github.com/LigphiDonk/Oh-my--paper/tree/main/skills/scientific-writing into .gemini/skills/scientific-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scientific-writing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LigphiDonk/Oh-my--paper scientific-writingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LigphiDonk/Oh-my--paper --skill scientific-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LigphiDonk/Oh-my--paper.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/scientific-writing .github/skills/scientific-writing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "scientific-writing" agent skill from https://github.com/LigphiDonk/Oh-my--paper/tree/main/skills/scientific-writing into .github/skills/scientific-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scientific-writing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LigphiDonk/Oh-my--paper --skill scientific-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LigphiDonk/Oh-my--paper scientific-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LigphiDonk/Oh-my--paper.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/scientific-writing .opencode/skills/scientific-writing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "scientific-writing" agent skill from https://github.com/LigphiDonk/Oh-my--paper/tree/main/skills/scientific-writing into .opencode/skills/scientific-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scientific-writing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
scientific-writingCore skill for the deep research and writing tool. An agent skill from LigphiDonk/Oh-my--paper.
Scientific Writing is an agent skill from LigphiDonk/Oh-my--paper. Core skill for the deep research and writing tool.
Its SKILL.md is about 6.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/citation_styles.md`, `references/figures_tables.md` and `references/imrad_structure.md`).
It sits in Research & Science, covering Scientific writing and Deep research. The repository describes itself as: A Claude Code plugin that turns your terminal into an autonomous research lab — literature survey, experiment execution, paper writing, all in one pipeline. The licence is MIT.
10 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 6baece9. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Scientific Writing loads about 6.5k tokens when it runs, and up to ~39k if it reads all its reference files. Until then it costs about 17 tokens; SKILL.md has 2,775 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from LigphiDonk/Oh-my--paper at commit 6baece9, republished under its MIT licence (© LigphiDonk). 2,775 words, ~6,492 tokens.
.claude/skills/scientific-writing/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process: (1) create section outlines with key points using research-lookup, (2) convert to flowing pros...
Use this skill when the user request matches its research workflow scope. Prefer the bundled resources instead of recreating templates or reference material. Keep outputs traceable to project files, citations, scripts, or upstream evidence.
references/ only when the current task needs the extra detail.This is the core skill for the deep research and writing tool—combining AI-driven deep research with well-formatted written outputs. Every document produced is backed by comprehensive literature search and verified citations through the research-lookup skill.
Scientific writing is a process for communicating research with precision and clarity. Write manuscripts using IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, and reporting guidelines (CONSORT/STROBE/PRISMA). Apply this skill for research papers and journal submissions.
Critical Principle: Always write in full paragraphs with flowing prose. Never submit bullet points in the final manuscript. Use a two-stage process: first create section outlines with key points using research-lookup, then convert those outlines into complete paragraphs.
This skill should be used when:
⚠️ MANDATORY: Every scientific paper MUST include at least 1-2 AI-generated figures using the scientific-schematics skill.
This is not optional. Scientific papers without visual elements are incomplete. Before finalizing any document:
How to generate figures:
How to generate schematics:
python scripts/generate_schematic.py "your diagram description" -o figures/output.pngThe AI will automatically:
When to add schematics:
For detailed guidance on creating schematics, refer to the scientific-schematics skill documentation.
IMRAD Format: Guide papers through the standard Introduction, Methods, Results, And Discussion structure used across most scientific disciplines. This includes:
For detailed guidance on IMRAD structure, refer to references/imrad_structure.md.
Alternative Structures: Support discipline-specific formats including:
Abstract Composition: Craft concise, standalone summaries (100-250 words) that capture the paper's purpose, methods, results, and conclusions. Support both structured abstracts (with labeled sections) and unstructured single-paragraph formats.
Introduction Development: Build compelling introductions that:
Methods Documentation: Ensure reproducibility through:
Results Presentation: Present findings with:
Discussion Construction: Synthesize findings by:
Apply citation styles correctly across disciplines. For comprehensive style guides, refer to references/citation_styles.md.
Major Citation Styles:
Best Practices:
Create effective data visualizations that enhance comprehension. For detailed best practices, refer to references/figures_tables.md.
When to Use Tables vs. Figures:
Design Principles:
Common Figure Types:
Ensure completeness and transparency by following established reporting standards. For comprehensive guideline details, refer to references/reporting_guidelines.md.
Key Guidelines:
Each guideline provides checklists ensuring all critical methodological elements are reported.
Apply fundamental scientific writing principles. For detailed guidance, refer to references/writing_principles.md.
Clarity:
Conciseness:
Accuracy:
Objectivity:
CRITICAL: Always write in full paragraphs, never submit bullet points in scientific papers.
Scientific papers must be written in complete, flowing prose. Use this two-stage approach for effective writing:
Stage 1: Create Section Outlines with Key Points
When starting a new section:
Example outline (Introduction section):
- Background: AI in drug discovery gaining traction
* Cite recent reviews (Smith 2023, Jones 2024)
* Traditional methods are slow and expensive
- Gap: Limited application to rare diseases
* Only 2 prior studies (Lee 2022, Chen 2023)
* Small datasets remain a challenge
- Our approach: Transfer learning from common diseases
* Novel architecture combining X and Y
- Study objectives: Validate on 3 rare disease datasetsStage 2: Convert Key Points to Full Paragraphs
Once the outline is complete, expand each bullet point into proper prose:
Example conversion to prose:
Artificial intelligence approaches have gained significant traction in drug discovery
pipelines over the past decade (Smith, 2023; Jones, 2024). While these computational
methods show promise for accelerating the identification of therapeutic candidates,
traditional experimental approaches remain slow and resource-intensive, often requiring
years of laboratory work and substantial financial investment. However, the application
of AI to rare diseases has been limited, with only two prior studies demonstrating
proof-of-concept results (Lee, 2022; Chen, 2023). The primary obstacle has been the
scarcity of training data for conditions affecting small patient populations.
To address this challenge, we developed a transfer learning approach that leverages
knowledge from well-characterized common diseases to predict therapeutic targets for
rare conditions. Our novel neural architecture combines convolutional layers for
molecular feature extraction with attention mechanisms for protein-ligand interaction
modeling. The objective of this study was to validate our approach across three
independent rare disease datasets, assessing both predictive accuracy and biological
interpretability of the results.Key Differences Between Outlines and Final Text:
| Outline (Planning Stage) | Final Manuscript |
|---|---|
| Bullet points and fragments | Complete sentences and paragraphs |
| Telegraphic notes | Full explanations with context |
| List of citations | Citations integrated into prose |
| Abbreviated ideas | Developed arguments with transitions |
| For your eyes only | For publication and peer review |
Common Mistakes to Avoid:
When Lists ARE Acceptable (Limited Cases):
Lists may appear in scientific papers only in specific contexts:
Integration with Research Lookup:
The research-lookup skill is essential for Stage 1 (creating outlines):
This two-stage process ensures you:
Adapt manuscripts to journal requirements:
Adapt language, terminology, and conventions to match the specific scientific discipline. Each field has established vocabulary, preferred phrasings, and domain-specific conventions that signal expertise and ensure clarity for the target audience.
Identify Field-Specific Linguistic Conventions:
Biomedical and Clinical Sciences:
Molecular Biology and Genetics:
Chemistry and Pharmaceutical Sciences:
Ecology and Environmental Sciences:
Physics and Engineering:
Neuroscience:
Social and Behavioral Sciences:
General Principles:
Match Audience Expertise:
Define Technical Terms Strategically:
Maintain Consistency:
Avoid Field Mixing Errors:
Verify Terminology Usage:
Top Rejection Reasons:
Writing Quality Issues:
Stage 1: Planning
Stage 2: Drafting (Use two-stage writing process for each section)
Remember: Bullet points are for planning only—the final manuscript must be in complete paragraphs.
Stage 3: Revision
Stage 4: Final Preparation
This skill works effectively with:
This skill includes comprehensive reference files covering specific aspects of scientific writing:
references/imrad_structure.md: Detailed guide to IMRAD format and section-specific contentreferences/citation_styles.md: Complete citation style guides (APA, AMA, Vancouver, Chicago, IEEE)references/figures_tables.md: Best practices for creating effective data visualizationsreferences/reporting_guidelines.md: Study-specific reporting standards and checklistsreferences/writing_principles.md: Core principles of effective scientific communicationLoad these references as needed when working on specific aspects of scientific writing.
© LigphiDonk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 5 other files (references) in skills/scientific-writing of LigphiDonk/Oh-my--paper.
Open the folder on GitHubat commit 6baece9
Scientific Writing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Scientific Writing this skillLigphiDonk/Oh-my--paper | 739 | — | ~6.5k | Automated safety check: Pass | MIT | |
| Academic Research PipelineImbad0202/academic-research-skills | 51k | — | ~15k | Automated safety check: Pass | Custom licence | |
| Academic Research Suite for CodexImbad0202/academic-research-skills-codex | 12k | — | ~12k | Automated safety check: Pass | Custom licence | |
| Scientific Writingneflibata-feng/MyArxiv-Agent | 126 | 18 repos | ~8.4k | Automated safety check: Notes | MIT | |
| Research ClawAlphaLab-USTC/ResearchClaw | 134 | — | ~578 | Automated safety check: Pass | MIT | |
| Journal Submission Researchhuangwb8/ChineseResearchLaTeX | 2.9k | — | ~1.2k | Automated safety check: Pass | MIT |
Imbad0202/academic-research-skills
Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.
Imbad0202/academic-research-skills-codex
A router skill that sends academic work such as literature reviews, drafting, citation checks, peer review and revision to the right workflow in the ARS suite.
neflibata-feng/MyArxiv-Agent
Core skill for the deep research and writing tool. An agent skill from neflibata-feng/MyArxiv-Agent.
AlphaLab-USTC/ResearchClaw
Complete AI research assistant with 6 core capabilities: paper discovery, deep reading notes, reading list management, research taste learning, idea generation, and paper writing.
huangwb8/ChineseResearchLaTeX
Researches a named academic journal's submission requirements, formatting rules, fees, review speed and community feedback, and writes one Chinese markdown report.
aiming-lab/AutoResearchClaw
Runs the ResearchClaw 23-stage autonomous pipeline from a topic, config file and output directory, from literature review through experiments to a written and reviewed paper.
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
LigphiDonk/Oh-my--paper
Searches and downloads legally accessible academic PDFs, OCRs them to Markdown, and organizes the results into a traceable, AI-readable literature library.
LigphiDonk/Oh-my--paper
Finds and clones missing code repositories for a chosen research idea, then writes a survey that maps academic concepts to their implementations.
LigphiDonk/Oh-my--paper
Turns experimental data such as CSV, JSON or TensorBoard logs into statistical significance tests, visualizations and a drafted Results section.
LigphiDonk/Oh-my--paper
Lays out principles for catching fake, mismatched, or inconsistently formatted citations in academic writing, checked through live web search.
LigphiDonk/Oh-my--paper
Runs a seven-step quality-control and exploration pipeline on scRNA-seq, CyTOF or flow cytometry data and writes a plain-language report of what it found.
Categories
Core skill for the deep research and writing tool. An agent skill from LigphiDonk/Oh-my--paper. Scientific Writing is an agent skill from LigphiDonk/Oh-my--paper. Core skill for the deep research and writing tool.
Scientific Writing fits situations like: tasks that involve Scientific writing; tasks that involve Deep research.
Run `npx skills add LigphiDonk/Oh-my--paper --skill scientific-writing -a claude-code`. Or copy the skill folder (skills/scientific-writing in LigphiDonk/Oh-my--paper) into .claude/skills/scientific-writing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LigphiDonk/Oh-my--paper --skill scientific-writing -a codex`. Or copy the skill folder (skills/scientific-writing in LigphiDonk/Oh-my--paper) into .agents/skills/scientific-writing in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LigphiDonk/Oh-my--paper --skill scientific-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scientific-writing, .gemini/skills/scientific-writing, .github/skills/scientific-writing and .opencode/skills/scientific-writing in your project.
Going by SKILL.md and its folder, Scientific Writing needs the command-line tools its instructions call (python). Our summary lists: Python 3.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Scientific Writing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 6.5k tokens (SKILL.md is roughly 26k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 32k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Scientific Writing: Academic Research Pipeline (Imbad0202/academic-research-skills, 51k stars), Academic Research Suite for Codex (Imbad0202/academic-research-skills-codex, 12k stars), Scientific Writing (neflibata-feng/MyArxiv-Agent, 126 stars) and Research Claw (AlphaLab-USTC/ResearchClaw, 134 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LigphiDonk (a GitHub user) maintains it in LigphiDonk/Oh-my--paper, which has 739 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on April 15, 2026.
Source: LigphiDonk/Oh-my--paper on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.