econ-visualization
Skill63 starsChanged 5 months agoMITView on GitHub
Create publication-quality charts and graphs for economics papers.
In this repository47 other files it gives its agents.
- install/claude.mdCLAUDE.md
- daskSkill
- geopandasSkill
- matplotlibSkill
- plotlySkill
- polarsSkill
- pymc-bayesian-modelingSkill
- scikit-learnSkill
- seabornSkill
- statistical-analysisSkill
- statsmodelsSkill
- pyfixestSkill
- python-panel-dataSkill
- r-econometricsSkill
- stata-data-cleaningSkill
- stata-regressionSkill
- wrdsSkill
- api-data-fetcherSkill
- citation-managementSkill
- datacommons-clientSkill
- exploratory-data-analysisSkill
- financial-text-nlpSkill
- literature-reviewSkill
- lit-review-assistantSkill
- openalex-apiSkill
- paper-2-acfin-webSkill
- research-ideationSkill
- research-lookupSkill
- sec-edgarSkill
- web-scrapeSkill
- academic-paper-writerSkill
- beamer-presentationSkill
- econ-humanizer-plusSkill
- econ-humanizerSkill
- econ-refereeSkill
- econ-slidesSkill
- econ-writeSkill
- econ-writing-plusSkill
- hypothesis-generationSkill
- latex-econ-modelSkill
- latex-postersSkill
- latex-tablesSkill
- paper-pdfSkill
- peer-reviewSkill
- scholar-evaluationSkill
- scientific-critical-thinkingSkill
- venue-templatesSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Follow these steps to complete the task:
- Distinctive: line 40
Before generating any code, ask the user:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Barrios Skills — John Barrios's curated workflow for economists and accountants. Prioritize reproducible empirical work, clear identification language, and journal-ready output.
Econ Visualization
Purpose
This skill creates publication-quality figures for economics papers, using clean styling, consistent scales, and export-ready formats.
When to Use
- Building figures for empirical results and descriptive analysis
- Standardizing chart style across a paper or presentation
- Exporting figures to PDF or PNG at journal quality
Instructions
Follow these steps to complete the task:
Step 1: Understand the Context
Before generating any code, ask the user:
- What is the dataset and key variables?
- What chart type is needed (line, bar, scatter, event study)?
- What output format and size are required?
Step 2: Generate the Output
Based on the context, generate code that:
- Uses a consistent theme for academic styling
- Labels axes and legends clearly
- Exports figures at high resolution
- Includes reproducible steps for data preparation
Step 3: Verify and Explain
After generating output:
- Explain how to regenerate or update the plot
- Suggest alternatives (log scales, faceting, smoothing)
- Note any data transformations used
Example Prompts
- "Create an event study plot with confidence intervals"
- "Plot GDP per capita over time for three countries"
- "Build a scatter plot with fitted regression line"
Example Output
# ============================================
# Publication-Quality Figure in R
# ============================================
library(tidyverse)
df <- read_csv("data.csv")
ggplot(df, aes(x = year, y = gdp_per_capita, color = country)) +
geom_line(size = 1) +
scale_y_continuous(labels = scales::comma) +
labs(
title = "GDP per Capita Over Time",
x = "Year",
y = "GDP per Capita (USD)",
color = "Country"
) +
theme_minimal(base_size = 12) +
theme(
legend.position = "bottom",
panel.grid.minor = element_blank()
)
ggsave("figures/gdp_per_capita.pdf", width = 7, height = 4, dpi = 300)Requirements
Software
- R 4.0+ or Python 3.10+
Packages
- For R:
ggplot2,scales,dplyr - For Python:
matplotlib,seaborn(optional alternative)
Best Practices
- Use vector formats (PDF, SVG) for publication
- Keep labels concise and readable
- Document data filters used in the figure
Common Pitfalls
- Overcrowded plots without clear labeling
- Inconsistent scales across figures
- Exporting low-resolution images
References
Changelog
v1.0.0
- Initial release
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

