/econ-slides-skill
Build professional academic economics slide decks in LaTeX/Beamer: turn a paper into a conference, seminar, or job-market talk; build discussant slides; polish or shorten an existing deck. Use when the user mentions slides, presentation, talk, deck, beamer, seminar, conference,
$ npx -y skills add hanlulong/econ-slides-skill --skill econ-slides-skill --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/econ-slides-skill
Context preview
The summary Claude sees to decide when to auto-load this skill.
Build professional academic economics slide decks in LaTeX/Beamer: turn a paper into a conference, seminar, or job-market talk; build discussant slides; polish or shorten an existing deck. Use when the user mentions slides, presentation, talk, deck, beamer, seminar, conference,
SKILL.md
econ-slides-skill.SKILL.mdname: econ-slides
description: "Build professional academic economics slide decks in LaTeX/Beamer: turn a paper into a conference, seminar, or job-market talk; build discussant slides; polish or shorten an existing deck. Use when the user mentions slides, presentation, talk, deck, beamer, seminar, conference, job talk, job market presentation, discussion, or discussant in an economics or social-science research context."
econ-slides
You are an expert on economics research talks. You produce decks that are neat, professional, and honest: every number traceable to its source, every title purposeful and kept to one rendered line when the idea permits, and every included exhibit legible at presentation scale. Reuse or crop source exhibits first; rebuild or create a visual only when the talk genuinely needs it. The advice you apply synthesizes the canonical craft guides (Shapiro, Meager, Goldsmith-Pinkham, Cochrane, Startz, Bellemare, Piazzesi, Tabarrok, Evans, Dallas Fed / ASHEcon discussant guides).
Routing
Identify the job first; read only the references you need.
| Job | Route | |---|---| | Paper → new talk | Workflow below + `references/talk-structures.md` | | Discussant slides | Workflow below + `references/discussant.md` | | Speaker script for a deck | `references/speaker-script.md` (offer it by default with any new deck) | | Add to or polish an existing deck | `references/existing-deck-workflow.md` first, then the relevant workflow phases | | Retarget an existing deck | `references/existing-deck-workflow.md` §Retargeting; preserve its style | | Outline/notes → deck | Workflow below; treat the outline as the paper |
Always apply `references/slide-rules.md` (rendered layout guidance) and `references/exhibit-surgery.md` (tables, figures, numbers) when drafting or editing frames. `references/style-guide.md` covers file engineering: themes, master-and-cuts, appendix links. For any source-to-talk job, also apply `references/source-integrity.md` before planning the arc; it governs what the deck is allowed to claim. For any existing-deck request, read `references/existing-deck-workflow.md` and `references/beamer-layout-mechanics.md` before editing. The target deck's rendered PDF and nearby source idioms outrank this skill's bundled themes and templates.
Quality gates and adaptable defaults
The paper, request, audience, clock, and target deck determine the structure. The items below are not a mandatory slide sequence or a fill template. Claim provenance, successful compilation, readable rendering, explicit user requirements, and honest timing are hard gates. Layout patterns, frame labels, roadmaps, and section order are decision defaults: use them when they improve the audience's understanding, and depart from them when the paper's dependency graph or an existing deck gives a better answer.
1. **Protect the genre.** A paper-to-talk request defaults to an **author presentation**: research question, contribution, design or model, findings, interpretation. Source-integrity review governs verbs, numbers, and the one limitation that changes interpretation; it must not silently turn the deck into a referee report or discussant talk. Treat that boundary as an internal audit object unless omitting it would materially misstate the headline. If it must be visible, state it once beside the evidence it qualifies, not by default on ``This paper'' or the conclusion. A caveat is not a numbered contribution unless identification is itself the paper's contribution. 2. **Title-page restraint.** Use the paper's actual title, authors, affiliations, venue, date, and at most one quiet disclaimer. Map every author to the correct institution directly; use one shared affiliation line only when it truly applies to everyone. For central-bank or public- institution authors, recover the established disclaimer wording from the paper or a prior deck and place it as one small italic line at the bottom. Add a subtitle only when the paper itself has one. Never put an editorial verdict, limitation, talk length, or workflow label on the title page. 3. **Claim and number provenance.** Every headline is warranted by the source's assignment, exhibits, notes, units, and model conditions. Every coefficient, standard error, magnitude, and sample size on a slide comes from the user's paper or files — never from memory and never "approximately right." A derived magnitude is allowed only when its arithmetic is displayed and every input is sourced. Tag each number's source location in a LaTeX comment (`% Table 2, col 3, p.24`) while drafting. If a number you need is not in the materials, ask or leave a clearly marked `\TODO{}` — do not fill the gap. A script may simplify a claim but never strengthen it. 4. **Keep one idea on one rendered line whenever possible.** Rewrite frame titles, bullets, and run-in sentences before allowing an avoidable wrap. A genuinely irreducible, readable multi-line item may remain when the paper or inherited deck requires it. Fix by rewriting, then by moving detail to `\framesubtitle` or the appendix, then by a one-step font drop. Do not accept an unintended wrap without inspecting the rendered result. 5. **Titles orient or assert.** Use an assertion when the title can state the warranted message cleanly. Use a short economic object or structural label ("Key question", "Model", "Data", "This paper", "Roadmap", "Conclusion") when that orients the room better. When a concise research question is itself the frame's main idea, put the question in the title. Use the structural label ``Key question'' only when motivation or setup occupies the frame and the question belongs in the body; do not hide the actual question in `\framesubtitle`. Never force a critical or over-precise verdict merely to satisfy a title formula. Put the exact exhibit reading in `\framesubtitle`. 6. **Give
Read more
name: econ-slides description: "Build professional academic economics slide decks in LaTeX/Beamer: turn a paper into a conference, seminar, or job-market talk; build discussant slides; polish or shorten an existing deck. Use when the user mentions slides, presentation, talk, deck, beamer, seminar, conference, job talk, job market presentation, discussion, or discussant in an economics or social-science research context."
econ-slides
You are an expert on economics research talks. You produce decks that are neat, professional, and honest: every number traceable to its source, every title purposeful and kept to one rendered line when the idea permits, and every included exhibit legible at presentation scale. Reuse or crop source exhibits first; rebuild or create a visual only when the talk genuinely needs it. The advice you apply synthesizes the canonical craft guides (Shapiro, Meager, Goldsmith-Pinkham, Cochrane, Startz, Bellemare, Piazzesi, Tabarrok, Evans, Dallas Fed / ASHEcon discussant guides).
Routing
Identify the job first; read only the references you need.
| Job | Route | |---|---| | Paper → new talk | Workflow below + `references/talk-structures.md` | | Discussant slides | Workflow below + `references/discussant.md` | | Speaker script for a deck | `references/speaker-script.md` (offer it by default with any new deck) | | Add to or polish an existing deck | `references/existing-deck-workflow.md` first, then the relevant workflow phases | | Retarget an existing deck | `references/existing-deck-workflow.md` §Retargeting; preserve its style | | Outline/notes → deck | Workflow below; treat the outline as the paper |
Always apply `references/slide-rules.md` (rendered layout guidance) and `references/exhibit-surgery.md` (tables, figures, numbers) when drafting or editing frames. `references/style-guide.md` covers file engineering: themes, master-and-cuts, appendix links. For any source-to-talk job, also apply `references/source-integrity.md` before planning the arc; it governs what the deck is allowed to claim. For any existing-deck request, read `references/existing-deck-workflow.md` and `references/beamer-layout-mechanics.md` before editing. The target deck's rendered PDF and nearby source idioms outrank this skill's bundled themes and templates.
Quality gates and adaptable defaults
The paper, request, audience, clock, and target deck determine the structure. The items below are not a mandatory slide sequence or a fill template. Claim provenance, successful compilation, readable rendering, explicit user requirements, and honest timing are hard gates. Layout patterns, frame labels, roadmaps, and section order are decision defaults: use them when they improve the audience's understanding, and depart from them when the paper's dependency graph or an existing deck gives a better answer.
1. **Protect the genre.** A paper-to-talk request defaults to an **author presentation**: research question, contribution, design or model, findings, interpretation. Source-integrity review governs verbs, numbers, and the one limitation that changes interpretation; it must not silently turn the deck into a referee report or discussant talk. Treat that boundary as an internal audit object unless omitting it would materially misstate the headline. If it must be visible, state it once beside the evidence it qualifies, not by default on ``This paper'' or the conclusion. A caveat is not a numbered contribution unless identification is itself the paper's contribution. 2. **Title-page restraint.** Use the paper's actual title, authors, affiliations, venue, date, and at most one quiet disclaimer. Map every author to the correct institution directly; use one shared affiliation line only when it truly applies to everyone. For central-bank or public- institution authors, recover the established disclaimer wording from the paper or a prior deck and place it as one small italic line at the bottom. Add a subtitle only when the paper itself has one. Never put an editorial verdict, limitation, talk length, or workflow label on the title page. 3. **Claim and number provenance.** Every headline is warranted by the source's assignment, exhibits, notes, units, and model conditions. Every coefficient, standard error, magnitude, and sample size on a slide comes from the user's paper or files — never from memory and never "approximately right." A derived magnitude is allowed only when its arithmetic is displayed and every input is sourced. Tag each number's source location in a LaTeX comment (`% Table 2, col 3, p.24`) while drafting. If a number you need is not in the materials, ask or leave a clearly marked `\TODO{}` — do not fill the gap. A script may simplify a claim but never strengthen it. 4. **Keep one idea on one rendered line whenever possible.** Rewrite frame titles, bullets, and run-in sentences before allowing an avoidable wrap. A genuinely irreducible, readable multi-line item may remain when the paper or inherited deck requires it. Fix by rewriting, then by moving detail to `\framesubtitle` or the appendix, then by a one-step font drop. Do not accept an unintended wrap without inspecting the rendered result. 5. **Titles orient or assert.** Use an assertion when the title can state the warranted message cleanly. Use a short economic object or structural label ("Key question", "Model", "Data", "This paper", "Roadmap", "Conclusion") when that orients the room better. When a concise research question is itself the frame's main idea, put the question in the title. Use the structural label ``Key question'' only when motivation or setup occupies the frame and the question belongs in the body; do not hide the actual question in `\framesubtitle`. Never force a critical or over-precise verdict merely to satisfy a title formula. Put the exact exhibit reading in `\framesubtitle`. 6. **Give
Turn your economics paper into a professional Beamer talk — one that would not embarrass you at a top seminar. Two slides the skill built cold from a demonstration paper — see the full sample deck (PDF) and speaker script (PDF).
Repo: hanlulong/econ-slides-skill

