Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

econ-writing-skill Skill

Repository ↗

by hanlulong★ 7281 skills

Install

What it does

Agent Skill that transforms AI assistants into expert economics paper writers. Synthesizes 50+ guides by Cochrane, McCloskey, Shapiro, Head, Bellemare, Goldin, Kremer. Compatible with Claude Code and OpenAI Codex.

  • Connects Instruction files the AI reads
  • Account or key No key found in README or SKILL.md
  • Category Coding
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/hanlulong-econ-writing-skill.svg)](https://mcp.popnx.com/en/skills/hanlulong-econ-writing-skill)

Use together with

MCP servers that connect the AI to services for the same work

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 468.8KUpdated 7 days ago

MCP · Connects a serviceRuns on your computer

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

by fallow-rsWidely used↓ 2.4M/wk★ 5.4KUpdated today

MCP · Connects a serviceRuns on your computer

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 740.3K/wk★ 10.4KUpdated yesterday

MCP · Connects a serviceRuns on your computer

Similar Skills

Same kind of work, ordered like the Skills list

Compared with similar ones
This one
econ-writing-skill
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
Makerhanlulongmorlutomultica-aiGraphify-Labsharry0703
Skills11111
GitHub stars728468,733234,332150,287144,566
Last code changeJul 20, 2026Nov 19, 2026Apr 20, 2026Nov 18, 2026Nov 18, 2026
LicenseMITMIT–Apache-2.0MIT

1 skills (instruction sets) by hanlulong that an AI reads and follows · not an MCP server

How a Skill differs from MCP

MCP = the hands

Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.

Skill = the manual

A text file that teaches the AI how to do a task. It connects to nothing.

Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.

Works with

Claude CodeCodex

From the maker’s README and the folders in the repo

Install

Is it safe?

  • Who made it

    GitHub account hanlulong (person), 10 years old

  • Use and upkeep

    ★ 728 stars · code last changed Jul 20, 2026

  • Any scripts?

    No, plain text files the AI reads and follows

  • Uses the internet?

    No scripts, so it does not go online by itself

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit f2bf7a2 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

First: which AI do you use?

Pick your app and this page shows only how to install it there

Option 1Upload to claude.ai (web and app)

Uploading to claude.ai would fail: the description is over 200 characters (548). Use "Let the AI install it" instead

Option 1Let Claude Code install it

Copy this sentence and paste it into a Claude Code chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Restart Claude Code, then type /econ-write or ask for a matching task and Claude picks it up

Checked against official docs Nov 12, 2026 · Source: code.claude.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.claude/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Claude Code, then type /econ-write or ask for a matching task and Claude picks it up

Skills you install yourself work in the ChatGPT desktop app, Codex CLI and the Codex IDE extension · ChatGPT on the web and mobile cannot use skills you install yourself, only skills that come with a plugin from the directory

ChatGPT desktop app

The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills

Option 1Let ChatGPT install it

Open Codex in the ChatGPT desktop app and paste this sentence into the chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Option 2Put the folder there yourself

Put the econ-write folder at ~/.agents/skills/econ-write

~ is your home folder ($HOME)

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

After installing

  • ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
  • To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
  • Codex picks up newly installed skills by itself; if one does not show up, restart Codex

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

ChatGPT on the web and mobile

Skills you install yourself do not work here; only skills that come with a plugin from the directory

To use this skill with ChatGPT, use the ChatGPT desktop app as above

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

Option 1Let Codex install it

Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Codex, then ask for a matching task; Codex lists the skill

Option 1Let Cursor install it

Copy this sentence and paste it into a Cursor chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

In Cursor’s Agent chat, type / and pick econ-write

Checked against official docs Nov 12, 2026 · Source: cursor.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.cursor/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. In Cursor’s Agent chat, type / and pick econ-write

Option 1Let the AI install it

For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.

View on GitHub ↗

Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026

View the original SKILL.md

The text below comes from the maker’s repo, not from PopNx MCP

Showing the first 8,000 characters · Open the full file on GitHub

---
name: econ-write
description: "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, structural, mixed) and all sections."
---

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).

---

# CORE PRINCIPLES

## 1. The #1 Rule: Reader First
"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.

## 2. Triangular / Newspaper Style
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).

## 3. One Central Contribution
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.

## 4. Concrete, Not Abstract
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."

## 5. Every Word Must Count
"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).

## 6. Active Voice, Present Tense
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.

## 7. Simple > Complex
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.

---

# WRITING THE ABSTRACT

## Formula
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)

## Structure (100-150 words)
1. **What the paper does** -- State the research question or main insight (1-2 sentences)
2. **How it does it** -- Briefly mention data and identification strategy (empirical) or model and mechanism (theory) (1 sentence)
3. **What it finds** -- State the central, concrete finding or result (1-2 sentences)
4. **Why it matters** -- Brief implication (optional, if space permits)

## Rules
- Be CONCRETE. Say what you find, not what you look for
- Do NOT mention other literature in the abstract (exception: one prior finding to establish a puzzle is acceptable if brief)
- Do NOT use passive voice
- Do NOT use jargon unnecessarily -- make it intelligible to a smart college-educated non-economist
- Do NOT exceed 150 words
- For empirical papers: include your identification strategy keyword (DiD, IV, RDD, RCT, etc.)
- For theory papers: name the mechanism or key economic force
- For structural papers: state the key counterfactual result

## Good Example
"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)

## Bad Example
"I analyze data on executive compensation and find many interesting results." (Cochrane's illustration of what NOT to write)

---

# WRITING THE INTRODUCTION

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.

## The Introduction Formula (Head / Evans / Bellemare)

### Paragraphs 1-2: THE HOOK (1-2 paragraphs)
Attract reader interest by connecting to something important. Four strategies:
- **Y matters**: when Y rises/falls, people are hurt or helped
- **Y is puzzling**: defies easy explanation or contradicts standard theory
- **Y is controversial**: economists disagree about it
- **Y is big or common**: large sector, widespread phenomenon

Start with a striking fact, a puzzle, or a bold claim grounded in data. Do NOT start with:
- Philosophy ("Financial economists have long wondered...")
- Literature ("The literature has long been interested in...")
- Policy motivation ("Given the importance of X for society...")
- A cute quotation
- "The literature lacks a model of..." (for theory papers, start with the economic puzzle, not the literature gap)

All of these are "clearing your throat" (Cochrane). Start with your contribution.

### Paragraph 3: THE RESEARCH QUESTION (1 paragraph)
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.

### Paragraphs 4-6: MAIN RESULTS (2-3 paragraphs)
State your key findings concretely. Top journals devote 25-30% of the introduction to results (Evans). Include:
- The central finding with magnitude and significance (empirical) or the main proposition and its intuition (theory)
- Key robustness results or extensions
- Economic significance (not just statistical significance)

### Paragraphs 7-9: LITERATURE REVIEW & VALUE ADDED (2-3 paragraphs)
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:**
- It is a STORY, not an annotated bibliography. The narrative hinges on a "however" or "although" -- here is what others have done, here is what remains incomplete, here is how this paper addresses it (Dudenhefer)
- Discuss only the 5-10 closest papers (closer to 5 is better)
- For each paper, explain what they did AND what limitation remains -- do not just state their finding
- Then describe approximately 3 contributions your paper makes:
  - Contribution to internal validity (better identification)
  - Contribution to external validity (new context, population)
  - Methodologi

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

From GitHub

GitHub stars
728
Maker
hanlulong
License
MIT
Last code change
Jul 20, 2026
SKILL.md files in the repo (including translated copies and templates)
3
Topics
academic-writing, agent-skills, ai, claude-code, codex, economics, latex, research-tools