latex-empirical-tables
Set up, format, fix, and clean up LaTeX regression and estimation tables in empirical economics or finance papers. Use when (a) creating a .tex, results.tex, main.tex, or preamble to display regression or estimation output from Python (pyfixest), Stata, or R — including any mention of estout, esttab, estauto, estwide, or table fragments; (b) formatting or repairing estout-style regression tables that overflow the right margin, have cramped or boxed notes, misaligned columns, or poor significance stars, or when asked to match a reference paper, make the note fill the table width, or choose a
npx skills add kennethkhoocy/applied-micro-skills --skill latex-empirical-tables --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Sets up, formats, fixes, and cleans LaTeX regression/estimation tables in empirical economics or finance papers. It handles building a results document from scratch, converting ugly estout-style fragments to the gold-standard pattern, and diagnosing Misplaced \omit errors from input-fragments. It covers various macros and environments (e.g., \estauto, \estwide, \estautoLT, \specialcell, \cmidrule) and manages notes positioning, multi-line headers, and alignment for estout-like outputs.
How it works
- Section A: Build a results document from scratch by creating an outline/ structure (outline/preamble/preamble.tex, outline/Tables/table_XX.tex, outline/results.tex) and inserting fragments with \estauto{Tables/table_01.tex}{N}{D{.}{.}{-1}} in a designated master document. It instructs saving each regression fragment to outline/Tables/table_XX.tex with auto-incrementing numbers and assembling a master results.tex with a standard preamble and document structure.
- It defines three macros for including table fragments without triggering Misplaced \omit: \estauto, \estwide, and \estautoLT, each wrapping a fragment with a specific tabular environment and using \@@input to avoid expansion issues. The macros require a fragment path, number of data columns, and a column spec, and are paired with a default decimal-aligned spec D{.}{.}{-1} when appropriate.
- It specifies the table fragment format: no top/bottom rules inside the fragment, right-aligned coefficients with p-values on the next line, and usage of \specialcell for multi-line names. Notes should be placed outside the tabular in a following minipage rather than inside the fragment.
- Section B describes converting existing ugly estout tables to the gold standard: ensuring wrapper macros use \@@input, using \estwide for wide tables, moving notes to a separate minipage, and keeping a consistent float pattern. It provides a minimal block to add to a preamble for the macros and guidance on handling self-contained tabular inputs and misaligned notes.
- It covers a pattern for choosing between \estwide, \estauto, and optional landscape/resizebox for very wide tables, and explains the special case of self-contained tabular inputs that embed notes inside the fragment.
When to use it
- When you need to create a new results.tex and supporting outline/ preamble from scratch for displaying regression output generated by Python (pyfixest), Stata, or R.
- When you must fix or reformat existing estout-style regression tables that overflow the right margin, have cramped notes, misaligned columns, or poor significance stars.
- When diagnosing a Misplaced \omit error from an input-ed table fragment inside a tabular environment.
- When merging several self-compiling block results.tex files into one master document, or when correcting table numbering with longtable and caption usage.
What it can touch
- outline/preamble/preamble.tex
- outline/Tables/table_XX.tex
- outline/results.tex
- Macros: \estauto, \estwide, \estautoLT, \specialcell, \sym
- Fragment files included via \@@input
Caveats
- Do NOT trigger for general LaTeX documents like beamer presentations, problem sets, letters, or CVs.
- Fragments should not include \toprule/\bottomrule; wrapper macros add these.
- Notes must be placed in a separate \begin{minipage}{\textwidth} block outside the tabular for proper formatting.
- The default column spec is D{.}{.}{-1} unless overridden; non-numeric content should use c.
- The tool relies on the presence of estout macros pre-defined in the preamble (or minimal subset listed in Section A of the skill).
# LaTeX Empirical Tables Empirical economics and finance papers export regression and estimation output as estout/esttab "body fragments" — rows of `\multicolumn` headers, coefficients with `\sym` stars, and parenthesised p-values or SEs, with no `\toprule`/`\bottomrule` — pulled into the manuscript through a wrapper macro (`\estauto`/`\estwide`/`\estautoLT`). Done well this reads like a top-journ
What does the latex-empirical-tables skill do?
Set up, format, fix, and clean up LaTeX regression and estimation tables in empirical economics or finance papers. Use when (a) creating a .tex, results.tex, main.tex, or preamble to display regression or estimation output from Python (pyfixest), Stata, or R — including any mention of estout, esttab, estauto, estwide, or table fragments; (b) formatting or repairing estout-style regression tables that overflow the right margin, have cramped or boxed notes, misaligned columns, or poor significance stars, or when asked to match a reference paper, make the note fill the table width, or choose a
How do I install it?
Run `npx skills add kennethkhoocy/applied-micro-skills --skill latex-empirical-tables --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kennethkhoocy/applied-micro-skills, a repository with 54 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.