academic-paper-writer
Draft economics papers with proper structure and academic style
What this skill does
# Academic Paper Writer
## Purpose
This skill helps economists draft, structure, and polish academic papers with proper conventions for economics journals. It provides templates for different paper types and guidance on academic writing style.
## When to Use
- Starting a new research paper from scratch
- Restructuring an existing draft
- Writing specific sections (introduction, literature review, conclusion)
- Preparing papers for journal submission
## Instructions
### Step 1: Identify Paper Type
Ask the user:
1. Is this empirical or theoretical?
2. What is the target journal/audience?
3. What stage is the paper at? (outline, first draft, revision)
4. What sections need help?
### Step 2: Follow the IMRAD Structure
For empirical papers, use:
1. **Introduction** - Motivation, research question, contribution
2. **Literature Review** - Related work and positioning
3. **Data & Methods** - Sources, sample, empirical strategy
4. **Results** - Main findings with tables/figures
5. **Discussion** - Interpretation, mechanisms, limitations
6. **Conclusion** - Summary and implications
### Step 3: Apply Economics Writing Conventions
- **First paragraph** should state the research question and main finding
- **Use present tense** for established facts, past tense for your findings
- **Be precise** with causal language (effect vs. association)
- **Cite heavily** in the literature review
- **Lead with results** in the results section
## Example Output: Introduction Template
```latex
\section{Introduction}
% Hook - Why does this matter?
[TOPIC] is a fundamental question in economics, with implications for
[POLICY AREA] and [BROADER RELEVANCE]. Despite extensive research,
we still lack clear evidence on [SPECIFIC GAP].
% Research question
This paper asks: [RESEARCH QUESTION IN PLAIN LANGUAGE]?
Specifically, we examine whether [PRECISE FORMULATION OF THE QUESTION].
% Preview of answer
We find that [MAIN RESULT IN ONE SENTENCE]. This effect is
[economically significant / modest / heterogeneous], with
[QUANTITATIVE SUMMARY: e.g., "a one standard deviation increase
in X associated with a Y percent increase in Z"].
% Methodology (brief)
To identify this effect, we exploit [IDENTIFICATION STRATEGY:
natural experiment / RCT / instrumental variable / RDD].
Our data come from [DATA SOURCE], covering [TIME PERIOD]
and [SAMPLE SIZE] observations.
% Contribution / Related literature
Our paper contributes to several strands of literature.
First, we extend the work of \citet{Author2020} by [EXTENSION].
Second, we provide new evidence on [MECHANISM/CHANNEL] that
complements \citet{OtherAuthor2019}. Finally, our findings
have implications for [POLICY/FUTURE RESEARCH].
% Roadmap
The remainder of the paper is organized as follows.
Section~\ref{sec:background} provides background and reviews
related literature. Section~\ref{sec:data} describes our data
and empirical strategy. Section~\ref{sec:results} presents our
main findings. Section~\ref{sec:robustness} discusses robustness
checks. Section~\ref{sec:conclusion} concludes.
```
## Example Output: Results Section Template
```latex
\section{Results}
\label{sec:results}
% Lead with the main finding
Table~\ref{tab:main} presents our main results. Column (1) shows
the baseline OLS specification without controls. The coefficient
on [TREATMENT VARIABLE] is [POINT ESTIMATE] (s.e. = [SE]),
statistically significant at the [1/5/10] percent level.
% Add controls incrementally
In column (2), we add [CONTROL SET 1]. The point estimate
[increases/decreases slightly/remains stable] to [ESTIMATE].
Column (3) includes [CONTROL SET 2] and adds [FIXED EFFECTS].
Our preferred specification in column (4) includes [FULL CONTROLS]
and yields [FINAL ESTIMATE].
% Interpret magnitude
To gauge economic significance, note that [INTERPRETATION].
A one standard deviation increase in [X] is associated with
a [Y] percent [increase/decrease] in [OUTCOME], or roughly
[COMPARISON TO MEAN/OTHER BENCHMARK].
% Brief mention of mechanisms/heterogeneity if relevant
Table~\ref{tab:hetero} explores heterogeneity by [DIMENSION].
We find that the effect is [larger/concentrated among]
[SUBGROUP], suggesting that [INTERPRETATION].
\begin{table}[htbp]
\centering
\caption{Main Results: Effect of X on Y}
\label{tab:main}
\begin{tabular}{lcccc}
\hline\hline
& (1) & (2) & (3) & (4) \\
& OLS & + Controls & + FE & Preferred \\
\hline
Treatment & 0.052*** & 0.048*** & 0.041** & 0.039** \\
& (0.012) & (0.011) & (0.015) & (0.016) \\
\\
Controls & No & Yes & Yes & Yes \\
Fixed Effects & No & No & Yes & Yes \\
Cluster SE & No & No & No & Yes \\
\\
Observations & 10,000 & 9,850 & 9,850 & 9,850 \\
R-squared & 0.05 & 0.12 & 0.35 & 0.35 \\
\hline\hline
\multicolumn{5}{l}{\footnotesize Notes: * p<0.10, ** p<0.05, *** p<0.01.} \\
\multicolumn{5}{l}{\footnotesize Standard errors in parentheses.} \\
\end{tabular}
\end{table}
```
## Example Output: Conclusion Template
```latex
\section{Conclusion}
\label{sec:conclusion}
% Restate question and answer
This paper examined [RESEARCH QUESTION]. Using [METHOD/DATA],
we found that [MAIN FINDING]. This result is robust to
[ROBUSTNESS CHECKS].
% Implications
Our findings have several implications. For policy, they suggest
that [POLICY IMPLICATION]. For theory, they provide support for
[THEORETICAL MECHANISM] and challenge [ALTERNATIVE VIEW].
% Limitations (brief, honest)
Several limitations warrant mention. First, [LIMITATION 1:
e.g., external validity]. Second, [LIMITATION 2: e.g.,
data constraints]. Future research could address these by
[SUGGESTION].
% Future directions
This paper opens several avenues for future work.
[DIRECTION 1]. [DIRECTION 2]. We hope our findings
stimulate further research on [BROADER TOPIC].
```
## Writing Tips
### For Introductions
- **First sentence should grab attention** - not "This paper examines..."
- **State your contribution clearly** - what's new about this paper?
- **Be specific about magnitudes** - don't just say "large effect"
- **Acknowledge limitations** preemptively in the last paragraph
### For Results
- **Lead with numbers** - put the coefficient in the first sentence
- **Interpret economically** - what does a 0.05 coefficient mean?
- **Guide the reader** through tables column by column
- **Don't oversell** - distinguish statistical from economic significance
### For Conclusions
- **Don't introduce new results** - synthesize what you've shown
- **Be honest about limitations** - reviewers will find them anyway
- **End on the contribution** - remind readers why this matters
## Common Pitfalls
- ❌ Burying the main result in the middle of the paper
- ❌ Using "significant" without specifying statistical or economic
- ❌ Over-claiming causality without proper identification
- ❌ Literature review that's just a list of papers
- ❌ Conclusion that's just a summary
## References
- [Cochrane (2005) Writing Tips for PhD Students](https://www.johnhcochrane.com/research-all/writing-tips-for-phd-studentsnbsp)
- [Shapiro (2019) How to Give an Applied Micro Talk](https://www.brown.edu/Research/Shapiro/pdfs/applied_micro_slides.pdf)
- [Thomson (2011) A Guide for the Young Economist](https://mitpress.mit.edu/books/guide-young-economist)
## Changelog
### v1.0.0
- Initial release with introduction, results, and conclusion templates
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.