Beamer
Noi1r/beamer-skill
Beamer LaTeX slide workflow: create, compile, review, and polish academic presentations.
Agent skill
Conference Talk Slides from Papers
by Orchestra-Research in Orchestra-Research/AI-Research-SKILLs
Generates Beamer LaTeX PDF and editable PPTX slides from a compiled paper, with speaker notes and an optional talk script, sized to four talk lengths.
Install Conference Talk Slides from Papers
$ npx skills add Orchestra-Research/AI-Research-SKILLs --skill presenting-conference-talks -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Orchestra-Research/AI-Research-SKILLs presenting-conference-talks --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Orchestra-Research/AI-Research-SKILLs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/20-ml-paper-writing/presenting-conference-talks .claude/skills/presenting-conference-talks && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "presenting-conference-talks" agent skill from https://github.com/Orchestra-Research/AI-Research-SKILLs/tree/main/20-ml-paper-writing/presenting-conference-talks into .claude/skills/presenting-conference-talks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "presenting-conference-talks", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Orchestra-Research/AI-Research-SKILLs/tree/main/20-ml-paper-writing/presenting-conference-talksType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Orchestra-Research/AI-Research-SKILLs --skill presenting-conference-talks -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Orchestra-Research/AI-Research-SKILLs presenting-conference-talks --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Orchestra-Research/AI-Research-SKILLs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/20-ml-paper-writing/presenting-conference-talks .agents/skills/presenting-conference-talks && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "presenting-conference-talks" agent skill from https://github.com/Orchestra-Research/AI-Research-SKILLs/tree/main/20-ml-paper-writing/presenting-conference-talks into .agents/skills/presenting-conference-talks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "presenting-conference-talks", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Orchestra-Research/AI-Research-SKILLs --skill presenting-conference-talks -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Orchestra-Research/AI-Research-SKILLs presenting-conference-talks --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Orchestra-Research/AI-Research-SKILLs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/20-ml-paper-writing/presenting-conference-talks .cursor/skills/presenting-conference-talks && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "presenting-conference-talks" agent skill from https://github.com/Orchestra-Research/AI-Research-SKILLs/tree/main/20-ml-paper-writing/presenting-conference-talks into .cursor/skills/presenting-conference-talks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "presenting-conference-talks", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Orchestra-Research/AI-Research-SKILLs.git --path 20-ml-paper-writing/presenting-conference-talks--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Orchestra-Research/AI-Research-SKILLs --skill presenting-conference-talks -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Orchestra-Research/AI-Research-SKILLs presenting-conference-talks --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Orchestra-Research/AI-Research-SKILLs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/20-ml-paper-writing/presenting-conference-talks .gemini/skills/presenting-conference-talks && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "presenting-conference-talks" agent skill from https://github.com/Orchestra-Research/AI-Research-SKILLs/tree/main/20-ml-paper-writing/presenting-conference-talks into .gemini/skills/presenting-conference-talks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "presenting-conference-talks", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Orchestra-Research/AI-Research-SKILLs presenting-conference-talksInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Orchestra-Research/AI-Research-SKILLs --skill presenting-conference-talks -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Orchestra-Research/AI-Research-SKILLs.git skills-src && mkdir -p .github/skills && cp -r skills-src/20-ml-paper-writing/presenting-conference-talks .github/skills/presenting-conference-talks && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "presenting-conference-talks" agent skill from https://github.com/Orchestra-Research/AI-Research-SKILLs/tree/main/20-ml-paper-writing/presenting-conference-talks into .github/skills/presenting-conference-talks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "presenting-conference-talks", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Orchestra-Research/AI-Research-SKILLs --skill presenting-conference-talks -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Orchestra-Research/AI-Research-SKILLs presenting-conference-talks --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Orchestra-Research/AI-Research-SKILLs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/20-ml-paper-writing/presenting-conference-talks .opencode/skills/presenting-conference-talks && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "presenting-conference-talks" agent skill from https://github.com/Orchestra-Research/AI-Research-SKILLs/tree/main/20-ml-paper-writing/presenting-conference-talks into .opencode/skills/presenting-conference-talks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "presenting-conference-talks", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
presenting-conference-talks- GitHub stars
- 13k
- Token cost
- ~2.5k tokens
- SKILL.md length
- 660 words
- Files
- 2 (incl. references)
- Skills in repo
- 96
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generates Beamer LaTeX PDF and editable PPTX slides from a compiled paper, with speaker notes and an optional talk script, sized to four talk lengths.
- Works in 4 steps: Content Extraction → Outline Generation → Slide-by-Slide Generation → …
- Preparing an oral or spotlight presentation for an ML or systems conference
- SKILL.md covers When to Use This Skill, Talk Types and Slide Counts, Slide Structure Templates and Systems Talk Specifics, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Slide counts follow the talk type: a poster talk runs 3 to 5 minutes with 5 to 8 slides, a spotlight 5 to 8 minutes with 8 to 12 slides, an oral 15 to 20 minutes with 15 to 22 slides, and an invited talk 30 to 45 minutes with 25 to 40 slides. Each type gets a slide-by-slide outline, with rules of thumb of about one slide per minute for orals and 1.5 for spotlights, and extra guidance for systems conference talks.
The output is a Beamer PDF for polished typesetting and a PPTX for last-minute edits, plus speaker notes and, optionally, a talk script. Slide templates are in `references/slide-templates.md`. Writing the paper itself, structuring a systems paper and making publication-quality plots are handed to the ml-paper-writing, systems-paper-writing and academic-plotting skills. The structure is credited as inspired by an ARIS paper-slides skill.
When your agent uses it
- Preparing an oral or spotlight presentation for an ML or systems conference
- Turning a compiled paper into Beamer slides with a PPTX copy
- Writing speaker notes and a talk script for a paper
- Planning slide counts for a short poster talk
Example prompts
- “Make a 15 minute oral deck from paper.pdf as Beamer and PPTX with speaker notes.”
- “Create a spotlight talk for our NSDI paper and include a talk script.”
- “Outline an invited talk for this paper with demo slides and hidden Q&A backups.”
Requirements
- A compiled paper to work from
- A LaTeX installation that can build Beamer slides
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 773a529. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are latex and python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
cs.utexas.edu
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Conference Talk Slides from Papers loads about 2.5k tokens when it runs, and up to ~6.3k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 660 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Orchestra-Research/AI-Research-SKILLs at commit 773a529, republished under its MIT licence (© Orchestra-Research). 660 words, ~2,529 tokens.
Download SKILL.mdSave it as
.claude/skills/presenting-conference-talks/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- presenting-conference-talks
- description
- Generates conference presentation slides (Beamer LaTeX PDF and editable PPTX) from a compiled paper with speaker notes and talk script. Use when preparing oral talks, spotlight presentations, or invited talks for ML and systems conferences.
- version
- 1.0.0
- author
- Orchestra Research
- license
- MIT
- tags
- Presenting Conference Talks, Beamer, PPTX, Slides, Speaker Notes, OSDI, SOSP, ASPLOS, NeurIPS, ICML
- dependencies
- python-pptx>=0.6.21
Presenting Conference Talks: From Paper to Slides
Generate conference presentation slides from a compiled research paper. Produces both Beamer LaTeX PDF (for polished typesetting) and editable PPTX (for last-minute adjustments), with speaker notes and an optional talk script.
When to Use This Skill
| Scenario | Use This Skill | Use Other Skills Instead |
|---|---|---|
| Preparing oral/spotlight/poster-talk slides | ✅ | |
| Generating Beamer PDF + PPTX from paper | ✅ | |
| Speaker notes and talk script | ✅ | |
| Writing the paper itself | ml-paper-writing | |
| Structuring a systems paper | systems-paper-writing | |
| Creating publication-quality plots | academic-plotting |
Attribution: This skill's structure draws inspiration from the ARIS paper-slides skill (570 lines, supporting poster/spotlight/oral/invited with Beamer+PPTX). This is an independent implementation for the AI-Research-SKILLs ecosystem.
Talk Types and Slide Counts
| Talk Type | Duration | Slides | Content Depth |
|---|---|---|---|
| poster-talk | 3–5 min | 5–8 | Problem + key result only |
| spotlight | 5–8 min | 8–12 | Problem + approach + key results |
| oral | 15–20 min | 15–22 | Full story with evaluation highlights |
| invited | 30–45 min | 25–40 | Deep dive with context and demos |
Rule of thumb: ~1 slide per minute for oral, ~1.5 slides per minute for spotlight.
Slide Structure Templates
Poster-Talk (5–8 slides)
Slide 1: Title + Authors + Affiliation
Slide 2: Problem — Why this matters (1 motivating figure)
Slide 3: Key Insight — One-sentence thesis
Slide 4: Approach Overview — Architecture diagram
Slide 5: Main Result — Headline numbers (1 figure)
Slide 6: Takeaway + QR code to paper/codeSpotlight (8–12 slides)
Slide 1: Title + Authors
Slide 2: Problem Statement — Concrete, quantified
Slide 3: Motivation — Why existing solutions fall short
Slide 4: Key Insight — Thesis statement
Slide 5: System Overview — Architecture diagram
Slide 6: Design Highlight 1 — Core mechanism
Slide 7: Design Highlight 2 — Key innovation
Slide 8: Evaluation Setup — Baselines and workloads (brief)
Slide 9: Main Results — Headline performance figure
Slide 10: Ablation / Breakdown — What contributes most
Slide 11: Summary + Contributions
Slide 12: Thank You + LinksOral (15–22 slides)
Slide 1: Title + Authors + Venue
Slide 2: Outline (optional — "roadmap" slide)
Slide 3: Problem Context — Domain importance
Slide 4: Problem Statement — Specific challenge
Slide 5: Motivation — Gaps in existing systems
Slide 6: Key Insight — Thesis
Slide 7: System Overview — Architecture diagram
Slide 8: Design Component 1 — Detailed walkthrough
Slide 9: Design Component 2 — Detailed walkthrough
Slide 10: Design Component 3 — Detailed walkthrough
Slide 11: Design Alternatives — Why not other approaches
Slide 12: Implementation — Key engineering highlights
Slide 13: Evaluation Setup — Testbed, baselines, metrics
Slide 14: End-to-End Results — Main performance
Slide 15: Result Deep Dive — Breakdown or per-workload
Slide 16: Ablation Study — Component contributions
Slide 17: Scalability — Scaling behavior
Slide 18: Demo Slide (systems talks) — Screenshot or recording
Slide 19: Related Work — Positioning (brief)
Slide 20: Summary — Contributions restated
Slide 21: Future Work — Open questions
Slide 22: Thank You + Paper Link + QR CodeInvited Talk (25–40 slides)
Extends the oral structure with:
- Additional context slides (field overview, historical progression)
- Multiple demo/walkthrough slides
- Deeper evaluation analysis
- Broader implications and future directions
- Q&A preparation slides (hidden, for backup)
Systems Talk Specifics
Systems conference talks have unique requirements compared to ML talks:
Demo Slide
- Include a live demo or pre-recorded screencast of the system in action
- Always have a recorded backup — live demos fail at the worst times
- Show the system under realistic load, not toy examples
Architecture Walkthrough
- Animate the architecture diagram: highlight components as you explain them
- Use Beamer
\only<N>or\onslide<N>for progressive reveal - Walk through a concrete request end-to-end through the system
Evaluation Highlights
- Select 2–3 strongest figures from the paper
- Annotate figures on slides (arrows, circles highlighting key points)
- State the takeaway before showing the figure ("Our system is 2x faster — here's the data")
Speaker Notes Guidelines
Structure per Slide
[Timing: X minutes]
[Key point to convey]
[Transition sentence to next slide]Mike Dahlin's Layered Approach
Apply "Say what you're going to say, say it, then say what you said" at three levels:
- Talk level: Outline slide → body → summary slide
- Section level: Section heading → content slides → section takeaway
- Slide level: Headline statement → supporting evidence → transition
Timing Guidelines
- Poster-talk: 30–60 sec per slide
- Spotlight: 30–45 sec per slide
- Oral: 45–90 sec per slide
- Invited: 60–120 sec per slide
Show full SKILL.md (265 more words)Show less
Output Formats
Beamer LaTeX → PDF
Advantages: Professional typesetting, math support, version control friendly.
\documentclass[aspectratio=169]{beamer}
\usetheme{metropolis} % Clean, modern theme
\usepackage{appendixnumberbeamer}
\title{Your Paper Title}
\subtitle{Venue Year}
\author{Author 1 \and Author 2}
\institute{Institution}
\date{}
\begin{document}
\maketitle
\begin{frame}{Problem}
\begin{itemize}
\item Key problem statement
\item Concrete motivation with numbers
\end{itemize}
\note{Speaker note: Start with the big picture...}
\end{frame}
% ... more frames ...
\end{document}python-pptx → Editable PPTX
Advantages: Easy last-minute edits, corporate template compatibility, animations.
from pptx import Presentation
from pptx.util import Inches, Pt
from pptx.enum.text import PP_ALIGN
prs = Presentation()
prs.slide_width = Inches(13.333) # 16:9
prs.slide_height = Inches(7.5)
# Title slide
slide = prs.slides.add_slide(prs.slide_layouts[0])
slide.shapes.title.text = "Your Paper Title"
slide.placeholders[1].text = "Author 1, Author 2\nVenue Year"
# Content slide
slide = prs.slides.add_slide(prs.slide_layouts[1])
slide.shapes.title.text = "Problem Statement"
body = slide.placeholders[1]
body.text = "Key point 1\nKey point 2"
# Add speaker notes
notes_slide = slide.notes_slide
notes_slide.notes_text_frame.text = "Speaker note: explain the motivation..."
prs.save("talk.pptx")Color Scheme Suggestions
These are aesthetic suggestions, not official venue requirements. Adjust freely.
| Venue Type | Primary | Accent | Background |
|---|---|---|---|
| USENIX (OSDI/NSDI) | Dark Blue (#003366) | Red (#CC0000) | White |
| ACM (SOSP/ASPLOS) | ACM Blue (#0071BC) | Dark Gray (#333333) | White |
| NeurIPS | Purple (#7B2D8E) | Gold (#F0AD00) | White |
| ICML | Teal (#008080) | Orange (#FF6600) | White |
| Generic | Dark Gray (#333333) | Blue (#0066CC) | White |
Workflow
Step 1: Content Extraction
- Read the compiled paper (PDF or LaTeX source)
- Identify: thesis, contributions, architecture figure, key eval figures
- Note the talk type and durationStep 2: Outline Generation
- Select the appropriate slide structure template (above)
- Map paper sections to slide groups
- Allocate time per slide groupStep 3: Slide-by-Slide Generation
- Generate Beamer source slide by slide
- Add speaker notes per slide
- Include figures from paper (copy to slides/ directory)
- Generate python-pptx script for PPTX versionStep 4: Review and Polish
- Check total slide count matches talk duration
- Verify all figures are readable at presentation resolution
- Run Beamer compilation: latexmk -pdf slides.tex
- Run PPTX generation: python3 generate_slides.py
- Review speaker notes for timing and transitionsQuick Checklist
- Slide count appropriate for talk type/duration
- Title slide has correct authors, affiliations, venue
- Architecture diagram included and clearly labeled
- Key eval figures annotated with takeaways
- Speaker notes include timing markers
- Transitions between sections are smooth
- Demo slide has recorded backup
- Thank-you slide includes paper link / QR code
- Font sizes ≥ 24pt for readability from back of room
- Consistent color scheme throughout
Common Issues and Solutions
| Issue | Solution |
|---|---|
| Too many slides for time limit | Cut details, keep one figure per point |
| Slides feel like paper paragraphs | Use bullet points (≤ 6 per slide), let figures tell the story |
| Audience lost during design section | Add architecture walkthrough with progressive reveal |
| Evaluation slides overwhelming | Show 2–3 strongest figures, put rest in backup slides |
| Speaker notes too long | Target 3–4 sentences per slide, focus on transitions |
| Beamer compilation fails | Check figure paths, use \graphicspath{{figures/}} |
| PPTX looks different from Beamer | Adjust python-pptx font sizes and margins manually |
References
- references/slide-templates.md — Complete Beamer template code and python-pptx generation script
- Mike Dahlin, "Giving a Conference Talk" — https://www.cs.utexas.edu/~dahlin/professional/goodTalk.pdf
© Orchestra-Research, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in 20-ml-paper-writing/presenting-conference-talks of Orchestra-Research/AI-Research-SKILLs.
- SKILL.md
- references/slide-templates.md
Open the folder on GitHubat commit 773a529
Compare with similar skills
Conference Talk Slides from Papers next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Conference Talk Slides from Papers this skillOrchestra-Research/AI-Research-SKILLs | 13k | — | ~2.5k | Automated safety check: Pass | MIT | |
| BeamerNoi1r/beamer-skill | 364 | — | ~13k | Automated safety check: Notes | MIT | |
| Powerpoint SlidesNoi1r/powerpoint-skill | 124 | — | ~12k | Automated safety check: Notes | MIT | |
| Explorable Deckclaesbackman/AI-research-feedback | 495 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Ambiguity Reportlawve-ai/awesome-legal-skills | 847 | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Oleafly Slides And PostersOleafly/Oleafly | 212 | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
Powerpoint Slides
Noi1r/powerpoint-skill
Create visually rich PowerPoint (.pptx) presentations from academic papers, research notes, or any content the user wants in slide format.
Explorable Deck
claesbackman/AI-research-feedback
Build a Quarto reveal.js slide deck in the explorable-explanation style (Nicky Case) — one idea per slide, assertion titles, a concrete running example, run-time SVG stages the presenter drives…
Ambiguity Report
lawve-ai/awesome-legal-skills
Turn an interpretive-ambiguity audit of a legal text — contract, statute, regulation, or judicial opinion — into a polished deliverable.
Oleafly Slides And Posters
Oleafly/Oleafly
Turn the manuscript in the open project into a talk deck or a conference poster and compile it in place.
Paper Slides
AI4Scientist/nano-scientist
Generate conference presentation slides (beamer LaTeX → PDF + editable PPTX) from a compiled paper, with speaker notes and full talk script.
More from Orchestra-Research/AI-Research-SKILLs
All 96 skills in this repoAudioCraft Audio Generation
Orchestra-Research/AI-Research-SKILLs
Generates music from text descriptions with MusicGen and sound effects with AudioGen, using Meta's AudioCraft PyTorch library with melody and style conditioning.
LLM Benchmarking with lm-evaluation-harness
Orchestra-Research/AI-Research-SKILLs
Runs lm-evaluation-harness to benchmark language models on academic suites such as MMLU, GSM8K and HumanEval, compare models and track training checkpoints.
Segment Anything Model Guide
Orchestra-Research/AI-Research-SKILLs
Guide to using Meta's Segment Anything Model for zero-shot image segmentation with point, box or mask prompts, or automatic mask generation.
Chroma Vector Database
Orchestra-Research/AI-Research-SKILLs
Shows how to store documents and embeddings in Chroma, query them by similarity with metadata filters, and persist them to disk for RAG and semantic search projects.
CLIP Image-Text Matching
Orchestra-Research/AI-Research-SKILLs
Explains OpenAI's CLIP model for zero-shot image classification, image-text similarity, semantic image search and content moderation, with install steps and code patterns.
Whisper Speech Recognition
Orchestra-Research/AI-Research-SKILLs
Transcribes audio with OpenAI's Whisper: 99 languages, translation to English, language detection, six model sizes and word-level timestamps, from Python or the CLI.
Related
Works with
Categories
Questions about Conference Talk Slides from Papers
What does Conference Talk Slides from Papers do?
Generates Beamer LaTeX PDF and editable PPTX slides from a compiled paper, with speaker notes and an optional talk script, sized to four talk lengths. Slide counts follow the talk type: a poster talk runs 3 to 5 minutes with 5 to 8 slides, a spotlight 5 to 8 minutes with 8 to 12 slides, an oral 15 to 20 minutes with 15 to 22 slides, and an invited talk 30 to 45 minutes with 25 to 40 slides.5 for spotlights, and extra guidance for systems conference talks.
When should I use Conference Talk Slides from Papers?
Conference Talk Slides from Papers fits situations like: preparing an oral or spotlight presentation for an ML or systems conference; turning a compiled paper into Beamer slides with a PPTX copy; writing speaker notes and a talk script for a paper; planning slide counts for a short poster talk.
How do I install Conference Talk Slides from Papers in Claude Code?
Run `npx skills add Orchestra-Research/AI-Research-SKILLs --skill presenting-conference-talks -a claude-code`. Or copy the skill folder (20-ml-paper-writing/presenting-conference-talks in Orchestra-Research/AI-Research-SKILLs) into .claude/skills/presenting-conference-talks in your project. Claude Code loads it when a task matches its description.
How do I install Conference Talk Slides from Papers in Codex?
Run `npx skills add Orchestra-Research/AI-Research-SKILLs --skill presenting-conference-talks -a codex`. Or copy the skill folder (20-ml-paper-writing/presenting-conference-talks in Orchestra-Research/AI-Research-SKILLs) into .agents/skills/presenting-conference-talks in your project. Codex loads it when a task matches its description.
Can I use Conference Talk Slides from Papers in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Orchestra-Research/AI-Research-SKILLs --skill presenting-conference-talks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/presenting-conference-talks, .gemini/skills/presenting-conference-talks, .github/skills/presenting-conference-talks and .opencode/skills/presenting-conference-talks in your project.
What does Conference Talk Slides from Papers need to run?
SKILL.md names no scripts, command-line tools or credentials: Conference Talk Slides from Papers is instructions for the agent only. Our summary lists: A compiled paper to work from; A LaTeX installation that can build Beamer slides.
Does Conference Talk Slides from Papers access the network?
SKILL.md names 1 domain. As links in the text: cs.utexas.edu. This is read from the text; nothing was executed.
Is Conference Talk Slides from Papers safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Conference Talk Slides from Papers use?
Conference Talk Slides from Papers is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Conference Talk Slides from Papers use?
About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.8k tokens, read only when the agent opens those files.
What are the alternatives to Conference Talk Slides from Papers?
Skills that share tags, products or a category with Conference Talk Slides from Papers: Beamer (Noi1r/beamer-skill, 364 stars), Powerpoint Slides (Noi1r/powerpoint-skill, 124 stars), Explorable Deck (claesbackman/AI-research-feedback, 495 stars) and Ambiguity Report (lawve-ai/awesome-legal-skills, 847 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conference Talk Slides from Papers?
Orchestra-Research (a GitHub organization) maintains it in Orchestra-Research/AI-Research-SKILLs, which has 13,405 GitHub stars. The repository holds 96 skills in this directory. The repository was last updated on June 16, 2026.
Source: Orchestra-Research/AI-Research-SKILLs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.