Econ Intro Writing
Guide for writing the introduction to an academic economics paper. Use this skill whenever the user asks for help writing, drafting, revising, or structuring an introduction to an economics paper - whether empirical micro, development economics, applied economics, or related fields. Also trigger when the user mentions "intro," "introduction section," "opening paragraphs," or asks how to motivate, frame, or present their research question in a paper. This skill synthesizes best practices from David Evans (CGDev), Keith Head, Claudia Sahm, Marc Bellemare, and Deirdre McCloskey.
Install
npx skills add dariia-m/my_claude_skills --skill econ-intro-writinggit clone --depth 1 https://github.com/dariia-m/my_claude_skills.git /tmp/my_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/my_claude_skills/econ_intro_writing ~/.claude/skills/econ-intro-writingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# How to Write the Introduction of an Economics Paper You win or lose your readers with the introduction. Research shows that economics papers with more readable introductions get cited more. The introduction is where you lay out your research question, your empirical strategy, your findings, and why it all matters - succinctly. This skill is based primarily on David Evans' analysis of introductions in top economics journals (AER, QJE, AEJ: Applied, etc.), supplemented by Keith Head's "Introduction Formula," Claudia Sahm's advice for job market papers, and Marc Bellemare's "Middle Bits Formula." ## The Core Structure Papers in top journals largely follow this pattern. There is variation, but the skeleton is remarkably consistent: 1. **Motivate with a puzzle or a problem** (1-2 paragraphs) 2. **Clearly state the research question** (1 paragraph) 3. **Describe the empirical approach** (1 paragraph) 4. **Present detailed results** (3-4 paragraphs) 5. **Establish value-added relative to related literature** (1-3 paragraphs) 6. **Optional extras**: robustness checks, policy relevance, limitations 7. **Roadmap of the paper** (1 paragraph) A typical introduction in a top journal runs about 10-15 paragraphs. It front-loads the paper's own contribution and pushes detailed literature discussion toward the end. --- ## Section-by-Section Guidance ### 1. The Motivation (1-2 paragraphs)
Details
- Skill name
econ-intro-writing- Repository
- dariia-m/my_claude_skills
- Path
econ_intro_writing/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Econ Intro Writing skill do?
Guide for writing the introduction to an academic economics paper. Use this skill whenever the user asks for help writing, drafting, revising, or structuring an introduction to an economics paper - whether empirical micro, development economics, applied economics, or related fields. Also trigger when the user mentions "intro," "introduction section," "opening paragraphs," or asks how to motivate, frame, or present their research question in a paper. This skill synthesizes best practices from David Evans (CGDev), Keith Head, Claudia Sahm, Marc Bellemare, and Deirdre McCloskey.
How do I install the Econ Intro Writing skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add dariia-m/my_claude_skills --skill econ-intro-writing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Econ Intro Writing popular?
It lives in dariia-m/my_claude_skills, which has 36 GitHub stars and 11 forks.
Related skills
Academic Paper Verify
36dariia-m/my_claude_skills
Thoroughly verify all code, tables, figures, modeling decisions, and quantitative claims in an academic paper against its source R scripts and output files. Use this skill whenever you need to audit, replicate, or verify an academic research paper - including cross-checking LaTeX tables against R output, validating econometric modeling choices, ensuring sample sizes are consistent, building a verification manifest, and running automated replication tests. Trigger this skill for any mention of: paper verification, replication check, table audit, code-paper consistency, reproducing results, veri
Academic Writing
36dariia-m/my_claude_skills
Activate when the user is drafting any academic economics content from scratch (e.g., outlines, abstracts, introductions, data/methods/identification sections, results narratives, conclusions, referee responses, table/figure captions) and needs economics-specific structure, phrasing options, and quality checks to produce publication-ready prose.
Anti Hallucination
36dariia-m/my_claude_skills
ALWAYS activate this skill. Apply these rules to every task regardless of domain. This skill governs how Claude Code verifies information, writes code, references documentation, and avoids fabricating functions, arguments, APIs, file paths, data structures, or facts. These rules override any inclination to guess.
Geordie
62ElliotJLT/Claude-Skill-Potions
When activated, respond entirely in Geordie dialect from Newcastle upon Tyne. Use proper Geordie words, phrases, and grammar. Reference Newcastle United players, legends, and lore when making analogies or celebrating wins. Channel the spirit of St James' Park, The Entertainers, and Wor Jackie himself. Howay the lads!
Econ Abstract Writing
36dariia-m/my_claude_skills
Guide for writing the abstract of an academic economics paper. Use this skill whenever the user asks for help writing, drafting, revising, or structuring an abstract for an economics paper - whether empirical micro, development economics, applied economics, or related fields. Also trigger when the user mentions "abstract," "paper summary," or asks how to compress their findings into a short description. This skill synthesizes best practices from David Evans (CGDev), Marc Bellemare, and patterns observed in top economics journals (AER, QJE, AEJ: Applied, etc.).
Naturalize Ukrainian
36dariia-m/my_claude_skills
Edit Ukrainian texts to sound natural without loss of meaning. Specialized for three problem types: (1) texts translated into Ukrainian (human, DeepL, Google Translate) that carry English or Russian syntax and calques; (2) texts written by AI directly in Ukrainian; (3) texts written by AI in English and then translated into Ukrainian - the worst case, combining AI cliches with translationese. Trigger whenever the user asks to edit, polish, naturalize, or de-AI a Ukrainian text, says a text "звучить як переклад", "звучить штучно", "звучить не по-людськи", asks to "відредагуй", "зроби природніши
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.