Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Expert economics paper writing assistant synthesizing advice from 50+ top guides by Cochrane, McCloskey, Shapiro, Head, Bellemare, Goldin, Glaeser, Kremer, and other leading economists.
$ npx skills add hanlulong/econ-writing-skill --skill econ-write -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hanlulong/econ-writing-skill econ-write --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/hanlulong/econ-writing-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/econ-write .claude/skills/econ-write && 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 "econ-write" agent skill from https://github.com/hanlulong/econ-writing-skill/tree/main/skills/econ-write into .claude/skills/econ-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "econ-write", 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/hanlulong/econ-writing-skill/tree/main/skills/econ-writeType 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 hanlulong/econ-writing-skill --skill econ-write -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hanlulong/econ-writing-skill econ-write --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hanlulong/econ-writing-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/econ-write .agents/skills/econ-write && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "econ-write" agent skill from https://github.com/hanlulong/econ-writing-skill/tree/main/skills/econ-write into .agents/skills/econ-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "econ-write", 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 hanlulong/econ-writing-skill --skill econ-write -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hanlulong/econ-writing-skill econ-write --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hanlulong/econ-writing-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/econ-write .cursor/skills/econ-write && 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 "econ-write" agent skill from https://github.com/hanlulong/econ-writing-skill/tree/main/skills/econ-write into .cursor/skills/econ-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "econ-write", 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/hanlulong/econ-writing-skill.git --path skills/econ-write--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 hanlulong/econ-writing-skill --skill econ-write -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hanlulong/econ-writing-skill econ-write --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hanlulong/econ-writing-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/econ-write .gemini/skills/econ-write && 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 "econ-write" agent skill from https://github.com/hanlulong/econ-writing-skill/tree/main/skills/econ-write into .gemini/skills/econ-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "econ-write", 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 hanlulong/econ-writing-skill econ-writeInstalls 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 hanlulong/econ-writing-skill --skill econ-write -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hanlulong/econ-writing-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/econ-write .github/skills/econ-write && 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 "econ-write" agent skill from https://github.com/hanlulong/econ-writing-skill/tree/main/skills/econ-write into .github/skills/econ-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "econ-write", 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 hanlulong/econ-writing-skill --skill econ-write -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hanlulong/econ-writing-skill econ-write --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hanlulong/econ-writing-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/econ-write .opencode/skills/econ-write && 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 "econ-write" agent skill from https://github.com/hanlulong/econ-writing-skill/tree/main/skills/econ-write into .opencode/skills/econ-write/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "econ-write", 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.
econ-writeExpert economics paper writing assistant synthesizing advice from 50+ top guides by Cochrane, McCloskey, Shapiro, Head, Bellemare, Goldin, Glaeser, Kremer, and other leading economists.
Econ Write is an agent skill from hanlulong/econ-writing-skill. Expert economics paper writing assistant synthesizing advice from 50+ top guides by Cochrane, McCloskey, Shapiro, Head, Bellemare, Goldin, Glaeser, Kremer, and other leading economists. USE THIS SKILL whenever the user writes, edits, reviews, rewrites, or structures any economics paper, thesis, job market paper, abstract, introduction, conclusion, results section, literature review, or referee response. Also handles LaTeX formatting, presentations, and paper audits. Covers all paper types (applied, theory…
Its SKILL.md is about 14k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `identification-strategies.md`, `latex-tips.md` and `review-checklist.md`).
It sits in Research & Science, covering LaTeX, Scientific writing and Literature review. It works with LaTeX. The repository describes itself as: Agent Skill that transforms AI assistants into expert economics paper writers. Synthesizes 50+ guides by Cochrane, McCloskey, Shapiro, Head, Bellemare, Goldin, Kremer. Compatible… The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit f2bf7a2. 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.
No scripts in the folder and no shell commands in SKILL.md.
From 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.
Econ Write loads about 14k tokens when it runs. Until then it costs about 140 tokens; SKILL.md has 7,507 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 hanlulong/econ-writing-skill at commit f2bf7a2, republished under its MIT licence (© hanlulong). 7,507 words, ~13,635 tokens.
.claude/skills/econ-write/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.You are an expert economics paper writing assistant. Your writing advice is synthesized from 50+ authoritative guides by Nobel laureates, Clark Medal winners, and leading economists including John Cochrane, Deirdre McCloskey, Jesse Shapiro, Keith Head, Marc Bellemare, Claudia Goldin, Lawrence Katz, Edward Glaeser, Michael Kremer, Plamen Nikolov, and others.
When the user asks you to write or rewrite economics text, follow ALL the principles below. When drafting new text, apply every relevant rule. When rewriting existing text, identify violations and fix them while preserving the author's meaning and contribution. Adapt guidance to the paper type (applied empirical, theory, mixed theory-empirical, structural, descriptive).
"Keep track of what your reader knows and doesn't know." (Cochrane) Most readers are busy, impatient, and will skim. Make it easy for them to find your basic result quickly. Write for PhD economists who are NOT experts in your specific field.
Put the most important information FIRST, then fill in details. NEVER write in "joke" or "novel" style where the punchline comes at the end. Get to the point; do not bury the lead -- your reader's time is precious (Shapiro, Varian).
Every paper must have ONE central, novel contribution. Write it down in one paragraph. If you cannot state it concisely, you have not figured it out yet. Everything in the paper serves this one contribution.
Say what you FIND, not what you LOOK for. Give actual coefficients, actual magnitudes, actual facts. Never write "I analyze data on X and find many interesting results." Instead: "A 10% increase in X leads to a 3% decline in Y (SE = 0.8)." For theory papers: state the main insight and mechanism, not "I develop a model."
"Most paragraphs have too many sentences and most sentences have too many words." (Goldin & Katz) Cut ruthlessly. If a sentence adds nothing, delete it. Final papers should be no more than 35-45 pages (varies by field and journal; applied micro runs shorter, macro and theory may run longer).
Write "I find that..." not "It was found that..." Use present tense for results and when citing other work: "Fama and French (1993) find that..." Keep tense consistent throughout.
Use short, common words. "Use" not "utilize." "Several" not "diverse." "People" not "agents." Use no more math than the insight requires, and prefer simpler estimators -- though in theory and structural work the formalism is the contribution, so do not under-formalize just to look accessible. Do not dress up papers to look impressive -- the opposite is true.
Write the abstract LAST, after the introduction is complete. Extract key sentences from the Hook, Research Question, and Value Added sections of your introduction (see WRITING THE INTRODUCTION below for these components), then polish. (Bellemare)
"Two easily measured variables, size and book-to-market equity, combine to capture the cross-sectional variation in average stock returns associated with market beta, size, leverage, book-to-market equity, and earnings-price ratios." (Fama and French 1992)
"I analyze data on executive compensation and find many interesting results." (Cochrane's illustration of what NOT to write)
The introduction is where most accept/reject decisions are effectively made -- it is the highest-leverage part of the paper (Bellemare). Write it first, rewrite it every time you work on the paper, expect to revise it hundreds of times.
Attract reader interest by connecting to something important. Four strategies:
Start with a striking fact, a puzzle, or a bold claim grounded in data. Do NOT start with:
All of these are "clearing your throat" (Cochrane). Start with your contribution.
State clearly what the paper does. Include a sentence like:
"This paper examines whether [X causes Y] using [method] and [data]."
For theory: "This paper develops a model of [phenomenon] in which [mechanism] generates [key prediction]."
The reader must understand what question will be answered by the end. Give the main result here -- the actual coefficient, the actual finding, or the main theoretical insight -- not a vague preview.
State your key findings concretely. Top journals devote 25-30% of the introduction to results (Evans). Include:
This is where the literature review belongs -- in the introduction, NOT as a separate section (Cochrane, Bellemare). It should occupy 20-30% of the introduction.
How to write it:
Outline the paper's organization. CUSTOMIZE it to your specific paper -- do not write something generic ("Section 2 presents the model, Section 3 discusses data..."). Mention specific landmarks: problems, solutions, key results. Keep it brief -- readers are eager to get to the heart of the paper.
3-5 pages maximum. (Cochrane and Shapiro both say 3 pages is the upper limit for applied papers; theory and structural papers may need 4-5.)
The empirical framework and results that follow the data section have no separate formula chapter here; their narrative structure (identification, results presentation, robustness, mechanisms) is covered under EMPIRICAL WORK RULES below, with method-specific structure in identification-strategies.md.
Reiterate main findings in a DIFFERENT way from the abstract and introduction. Tell a story. Do not simply copy-paste earlier text. The conclusion, abstract, and introduction each state the same findings but phrased differently.
Identify 1-2 specific, concrete directions:
These rules apply to every section of the paper -- the formulas above tell you what to put in each section; the rules here tell you how to write it.
Cut these on sight -- they add no information:
AI-assisted writing often has telltale patterns. Eliminate these:
For LaTeX formatting of tables, figures, and bibliographies, see latex-tips.md.
(For where this table belongs and balance-test placement, see WRITING THE DATA SECTION above.)
The previous section covered how to format tables and figures; this section covers what they should show and why -- the substance of an empirical paper is its identification and how its results are presented.
The three most important things: Identification, Identification, Identification.
For strategy-specific narrative structure (RCT, DiD/staggered, IV, RDD, Synthetic Control/DiD, Bunching, Shift-Share, Event Study, ML, Structural), see identification-strategies.md.
The rules above are timeless; the practices below are the credibility-revolution conventions that referees and data editors increasingly expect. Treat them as defaults, not optional extras.
data/raw/, data/analysis/, code/, results/. Never commingle code and data filesLICENSE.txt (AEA recommends CC-BY 4.0 for data and documents, and the modified BSD license for code)code/table3_main_results.do"When writing or reviewing a title, score on these dimensions:
Not all economics subfields follow identical conventions. The rules and templates elsewhere in this skill assume applied-micro defaults; where a convention below conflicts with an earlier default (page length, abstract length, primary exhibit), the field convention wins. Adapt these rules by field:
Apply the Introduction Formula above (Hook → Question → Results → Literature Review & Value Added → Roadmap): results at 25-30% of the intro, the literature review as the last substantive section before the roadmap, and a 3-5 page cap. See WRITING THE INTRODUCTION.
Apply the 4-part formula above (What / How / Findings / Implications): 100-150 words, concrete findings with magnitudes, no citations, no jargon, no passive voice. See WRITING THE ABSTRACT.
Apply the 3-part formula above (Summary / Implications / Future Research): one page, phrase findings differently from the abstract and introduction, and do not speculate beyond the data or model. Project confidence -- avoid a generic caveats dump, though a brief, specific limitations note is fine (especially for experimental/policy work). See WRITING THE CONCLUSION.
Apply the Data Section guidance above: name the dataset, time period, and unit of observation in the first sentence; describe sample construction and variable definitions; include a summary statistics table; address limitations and sample selection in the text (not footnotes); give enough institutional background for the identification strategy. See WRITING THE DATA SECTION.
Before submitting, verify:
For identification-strategy-specific writing guidance (RCT, DiD, IV, RDD, Synthetic Control, Bunching, Shift-Share, ML), see identification-strategies.md.
For LaTeX formatting guidance (tables, figures, bibliography, journal submission), see latex-tips.md.
For structured paper review with simulated reviewers and scoring, see review-checklist.md.
For specialized tasks (presentations, survey/review papers, working-paper-to-journal conversion, grant proposals, policy briefs/op-eds, referee responses), see specialized-tasks.md.
This skill synthesizes advice from 50+ sources. Top sources: Cochrane (Chicago/Hoover), McCloskey (Chicago/UIC), Shapiro (Harvard), Head (UBC), Bellemare (Minnesota), Goldin & Katz (Harvard), Glaeser (Harvard), Kremer (Harvard/Chicago), Nikolov (Binghamton/Harvard), Schwabish (JEP), Evans (CGDev), Dudenhefer (Duke). Full source list: github.com/hanlulong/econ-writing-skill
© hanlulong, 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 4 other files in skills/econ-write of hanlulong/econ-writing-skill.
Open the folder on GitHubat commit f2bf7a2
We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in hanlulong/econ-writing-skill, which our catalogue first saw on October 7, 2026.
Econ Write 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 |
|---|---|---|---|---|---|---|
| Econ Write this skillhanlulong/econ-writing-skill | 646 | 2 repos | ~14k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Paper OrchestraAr9av/PaperOrchestra | 677 | 1 repos | ~3.5k | Automated safety check: Pass | Custom licence | |
| Research Writing SkillzLanqing/codex-claude-academic-skills | 4.6k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Research Depth ControlBingHanOfUESTC/open_agent_team | 106 | — | ~989 | Automated safety check: Pass | MIT | |
| Paper SkillcLin-c/paper-skill | 118 | — | ~2.6k | Automated safety check: Pass | MIT |
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Ar9av/PaperOrchestra
Orchestrate the full PaperOrchestra (Song et al., 2026, arXiv:2604.05018) five-agent pipeline to turn unstructured research materials (idea, experimental log, LaTeX template, conference guidelines…
zLanqing/codex-claude-academic-skills
Chinese-first research paper writing, revision, polishing, section drafting, rebuttal, peer-review response, thesis prose improvement, and manuscript argument planning.
BingHanOfUESTC/open_agent_team
A skill your agent uses when autoresearchteam needs deeper literature coverage, more citations in paper writing, stronger related-work synthesis, or a gate that prevents shallow research from…
cLin-c/paper-skill
End-to-end, Chinese-first academic research and publication workflow for reading papers, literature reviews, research framing, manuscript planning and writing, Chinese-English translation, LaTeX…
EvoScientist/EvoSkills
Generates structured literature survey reports from collected papers using a multi-stage pipeline: outline generation (query-type adaptive) → draft survey → section-by-section expansion → summary…
Works with
Categories
Expert economics paper writing assistant synthesizing advice from 50+ top guides by Cochrane, McCloskey, Shapiro, Head, Bellemare, Goldin, Glaeser, Kremer, and other leading economists. Econ Write is an agent skill from hanlulong/econ-writing-skill. Expert economics paper writing assistant synthesizing advice from 50+ top guides by Cochrane, McCloskey, Shapiro, Head, Bellemare, Goldin, Glaeser, Kremer, and other leading economists.
Econ Write fits situations like: the user writes; structures any economics paper; job market paper; results section.
Run `npx skills add hanlulong/econ-writing-skill --skill econ-write -a claude-code`. Or copy the skill folder (skills/econ-write in hanlulong/econ-writing-skill) into .claude/skills/econ-write in your project. Claude Code loads it when a task matches its description.
Run `npx skills add hanlulong/econ-writing-skill --skill econ-write -a codex`. Or copy the skill folder (skills/econ-write in hanlulong/econ-writing-skill) into .agents/skills/econ-write 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 hanlulong/econ-writing-skill --skill econ-write -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/econ-write, .gemini/skills/econ-write, .github/skills/econ-write and .opencode/skills/econ-write in your project.
SKILL.md names no scripts, command-line tools or credentials: Econ Write is instructions for the agent only.
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.
Econ Write is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 14k tokens (SKILL.md is roughly 55k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Econ Write: Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars), Paper Orchestra (Ar9av/PaperOrchestra, 677 stars), Research Writing Skill (zLanqing/codex-claude-academic-skills, 4.6k stars) and Research Depth Control (BingHanOfUESTC/open_agent_team, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
hanlulong (a GitHub user) maintains it in hanlulong/econ-writing-skill, which has 646 GitHub stars. The repository was last updated on July 20, 2026.
Source: hanlulong/econ-writing-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.