agentleFS
Barrios88Barrios88/barrios-skills/skills/writing-and-review/beamer-presentation/SKILL.md

beamer-presentation

Skill63 starsChanged 5 months agoMITView on GitHub

Create academic presentations in Beamer with professional themes

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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
  1. Distinctive:

    Do they have specific style preferences?

    line 43
  2. Distinctive:

    Minimal text: - use bullets of 3-6 words

    line 56
  3. Distinctive:

    Consistent colors: - use a limited palette

    line 58
  4. Distinctive:

    One message per slide: - if you need more, split it

    line 300
  5. Distinctive:

    Use figures over tables: when possible

    line 301

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Barrios Skills — John Barrios's curated workflow for economists and accountants. Prioritize reproducible empirical work, clear identification language, and journal-ready output.

Beamer Presentation Creator

Purpose

This skill helps economists create professional academic presentations using LaTeX Beamer. It provides templates for conference talks, job market presentations, and seminar presentations with proper structure and clean aesthetics.

When to Use

  • Preparing conference presentations
  • Creating job market talk slides
  • Making seminar/workshop presentations
  • Converting a paper into presentation slides

Instructions

Step 1: Understand the Context

Ask the user:

  1. What type of presentation? (20-min conference, 90-min seminar, job market)
  2. What's the paper/project about?
  3. What's the target audience expertise level?
  4. Do they have specific style preferences?

Step 2: Structure by Time

DurationStructure
15-20 minMotivation (2) → Question (1) → Method (2) → Results (3-4) → Conclusion (1)
45-60 minAdd literature review, more results detail, robustness
90 minFull seminar with theoretical framework, extensive empirics

Step 3: Follow Presentation Best Practices

  • One idea per slide
  • Minimal text - use bullets of 3-6 words
  • Big fonts - minimum 20pt for content
  • Consistent colors - use a limited palette
  • Reveal incrementally using \pause or <+-> for complex slides

Example Output

\documentclass[aspectratio=169, 11pt]{beamer}

% ============================================
% THEME AND APPEARANCE
% ============================================

% Clean minimal theme
\usetheme{metropolis}
\usecolortheme{default}

% Or for a more traditional look:
% \usetheme{Madrid}
% \usecolortheme{whale}

% Custom colors
\definecolor{darkblue}{RGB}{0, 51, 102}
\definecolor{lightgray}{RGB}{245, 245, 245}

\setbeamercolor{frametitle}{bg=darkblue, fg=white}
\setbeamercolor{title}{fg=darkblue}
\setbeamercolor{structure}{fg=darkblue}

% Remove navigation symbols
\setbeamertemplate{navigation symbols}{}

% Frame numbers
\setbeamertemplate{footline}[frame number]

% ============================================
% PACKAGES
% ============================================

\usepackage{graphicx}
\usepackage{booktabs}
\usepackage{tikz}
\usepackage{pgfplots}
\pgfplotsset{compat=1.17}

% ============================================
% TITLE PAGE
% ============================================

\title{The Effect of X on Y: \\Evidence from Z}
\subtitle{Short and Descriptive}
\author{Your Name}
\institute{Your University}
\date{Conference Name \\ Month Year}

\begin{document}

% Title slide
\begin{frame}[plain]
    \titlepage
\end{frame}

% ============================================
% MOTIVATION (2-3 slides)
% ============================================

\begin{frame}{Motivation: Why This Matters}
    \begin{itemize}
        \item<1-> \textbf{Big picture:} [One sentence on broad relevance]
        \item<2-> \textbf{Specific puzzle:} [What we don't know]
        \item<3-> \textbf{Stakes:} [Why should we care?]
    \end{itemize}
    
    \vspace{1em}
    
    \only<4>{
    \begin{block}{Key Statistic}
        \Large \textbf{X\%} of [outcome] can be explained by [factor]
    \end{block}
    }
\end{frame}

\begin{frame}{What We Know (and Don't Know)}
    \textbf{Previous literature:}
    \begin{itemize}
        \item Author et al. (2020): Finding 1
        \item Other Author (2019): Finding 2
    \end{itemize}
    
    \vspace{1em}
    
    \textbf{Gap we fill:}
    \begin{itemize}
        \item[\textcolor{red}{?}] [Open question our paper addresses]
    \end{itemize}
\end{frame}

% ============================================
% RESEARCH QUESTION (1 slide)
% ============================================

\begin{frame}{This Paper}
    \begin{center}
        \Large
        \textbf{Research Question:} \\[1em]
        Does [X] cause [Y]? \\[2em]
    \end{center}
    
    \textbf{Preview of findings:}
    \begin{itemize}
        \item Main result in plain language
        \item Key magnitude: [Quantitative summary]
    \end{itemize}
\end{frame}

% ============================================
% EMPIRICAL STRATEGY (2-3 slides)
% ============================================

\begin{frame}{Data}
    \textbf{Sources:}
    \begin{itemize}
        \item Dataset 1: [Description, years, N]
        \item Dataset 2: [Description, matching method]
    \end{itemize}
    
    \vspace{1em}
    
    \textbf{Sample:}
    \begin{itemize}
        \item Unit of observation: [What is an observation?]
        \item Final sample: [N] observations, [Time period]
    \end{itemize}
\end{frame}

\begin{frame}{Identification Strategy}
    \textbf{Challenge:} [Endogeneity concern in one sentence]
    
    \vspace{1em}
    
    \textbf{Solution:} We exploit [natural experiment / instrument / RDD]
    
    \vspace{1em}
    
    \textbf{Key assumption:} [Identification assumption in plain language]
    
    \begin{equation*}
        Y_{it} = \alpha + \beta \cdot \text{Treatment}_{it} + \gamma X_{it} + \mu_i + \delta_t + \varepsilon_{it}
    \end{equation*}
\end{frame}

% ============================================
% RESULTS (3-5 slides)
% ============================================

\begin{frame}{Main Result}
    \begin{center}
        \includegraphics[width=0.8\textwidth]{figures/main_result.pdf}
    \end{center}
    
    \vspace{0.5em}
    
    \textbf{Takeaway:} [One sentence interpretation]
\end{frame}

\begin{frame}{Main Result: Regression Table}
    \begin{table}
        \centering
        \small
        \begin{tabular}{lccc}
            \toprule
            & (1) & (2) & (3) \\
            & OLS & + Controls & + FE \\
            \midrule
            Treatment & 0.052*** & 0.048*** & 0.041** \\
                      & (0.012)  & (0.011)  & (0.015) \\
            \midrule
            Controls & No & Yes & Yes \\
            Fixed Effects & No & No & Yes \\
            N & 10,000 & 9,850 & 9,850 \\
            \bottomrule
        \end{tabular}
    \end{table}
    
    \textbf{Economic magnitude:} 1 SD increase in X $\rightarrow$ Y\% increase in outcome
\end{frame}

\begin{frame}{Robustness Checks}
    \begin{itemize}
        \item[\checkmark] Alternative specifications
        \item[\checkmark] Placebo tests
        \item[\checkmark] Different sample cuts
        \item[\checkmark] [Other relevant checks]
    \end{itemize}
    
    \vspace{1em}
    
    $\rightarrow$ Results robust across specifications
\end{frame}

% ============================================
% CONCLUSION (1 slide)
% ============================================

\begin{frame}{Takeaways}
    \begin{enumerate}
        \item \textbf{Finding 1:} [Main result]
        \item \textbf{Finding 2:} [Secondary result]
        \item \textbf{Implication:} [Policy/theory takeaway]
    \end{enumerate}
    
    \vspace{2em}
    
    \begin{center}
        \Large Thank you! \\[0.5em]
        \normalsize your.email@university.edu
    \end{center}
\end{frame}

% ============================================
% APPENDIX
% ============================================

\appendix

\begin{frame}[noframenumbering]{Appendix: Additional Results}
    [Backup slides for Q\&A]
\end{frame}

\end{document}

Theme Recommendations

AudienceThemeNotes
AcademicmetropolisClean, modern, minimal
ConferenceMadridTraditional, professional
Job marketdefault with custom colorsSafe, customizable
PolicyCambridgeUSAuthoritative look

Best Practices

  1. One message per slide - if you need more, split it
  2. Use figures over tables when possible
  3. Highlight key numbers in results tables
  4. Build complex slides incrementally with \pause
  5. Prepare backup slides for anticipated questions
  6. Practice timing - 1-2 minutes per slide max

Common Pitfalls

  • ❌ Too much text on slides
  • ❌ Reading slides word-for-word
  • ❌ Tables with too many columns
  • ❌ Skipping the roadmap/preview
  • ❌ Ending with "Questions?" instead of takeaways

References

Changelog

v1.0.0

  • Initial release with conference talk template

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.