agentleFS
texra-aitexra-ai/texra-scientific-skills/skills/scientific-presenter/SKILL.md

scientific-presenter

Skill4 starsChanged 7 months agoMITView on GitHub

Build or revise scientific talks, posters, and Beamer slide decks from papers, codebases, figures, or LaTeX templates. Use when Codex needs to turn technical research into a clear presentation, preserve an existing slide theme, generate or improve figures, or iteratively compile and visually check presentation output.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for research talks, posters, code walkthrough decks, paper-to-slides conversions, and presentation revisions where visual …

    line 10
  2. Very specific:

    Read any provided .tex, .sty, poster template, or slide template before planning content.

    line 14
  3. Distinctive:

    Prefer visual communication.

    line 17
  4. Distinctive:

    Keep code excerpts short and purposeful.

    line 18
  5. Distinctive:

    If figures or plots are generated from code, rerun the code when feasible and verify the resulting assets instead of mocking them by …

    line 20
  6. Distinctive:

    Keep body text readable at presentation scale.

    line 24
  7. Distinctive:

    Use equations sparingly and only when they clarify the argument.

    line 25
  8. Distinctive:

    Keep aspect ratios intact for figures and ensure axes, legends, and units are visible.

    line 26
  9. Distinctive:

    Use progressive disclosure when the audience must absorb a derivation, algorithm, or workflow in stages.

    line 27
  10. Distinctive:

    Treat visual QA as mandatory.

    line 28

≈ “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

Scientific Presenter

When to use this skill

Use this skill for research talks, posters, code walkthrough decks, paper-to-slides conversions, and presentation revisions where visual quality matters as much as technical accuracy.

Workflow

  1. Read any provided .tex, .sty, poster template, or slide template before planning content. Preserve the existing theme, typography, colors, macros, and structure unless the user asks for a redesign.
  2. Survey the workspace before editing. Identify the core claims, algorithms, figures, tables, equations, and code artifacts that actually belong in the presentation.
  3. Plan the deck around a story rather than around the paper's section order. Make each slide answer one question or advance one idea.
  4. Prefer visual communication. Turn architecture, pipelines, derivations, and comparisons into diagrams, tables, overlays, or compact equations instead of dense prose blocks.
  5. Keep code excerpts short and purposeful. Show only the lines needed to explain the mechanism, result, or design decision.
  6. Compile early and often. After each substantial change, inspect the rendered output and fix layout, overflow, readability, and figure quality issues before continuing.
  7. If figures or plots are generated from code, rerun the code when feasible and verify the resulting assets instead of mocking them by description.

Quality Bar

  • Keep body text readable at presentation scale. Split crowded slides instead of shrinking everything.
  • Use equations sparingly and only when they clarify the argument. Define notation before using it on slides.
  • Keep aspect ratios intact for figures and ensure axes, legends, and units are visible.
  • Use progressive disclosure when the audience must absorb a derivation, algorithm, or workflow in stages.
  • Treat visual QA as mandatory. A slide that compiles but clips, overlaps, or hides labels is not done.

For a stricter final pass, use references/slide-quality-checklist.md to review slide density, figure quality, poster layout, and Beamer-specific issues.

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.