agentleFS
ShaishavMaisuriaShaishavMaisuria/research-paper-lifecycle-skills/skills/make-poster/SKILL.md

make-poster

Skill59 starsChanged 5 months agoApache-2.0View on GitHub

Creates and checks conference research posters and short poster-session pitches. Use when the user asks to make a poster, prepare a research poster, adapt a paper into a poster, fit a poster to A0/A1/36x48in, check a beamerposter or tikzposter file, reuse paper figures, or write a 2-minute or 5-minute poster pitch. Bundled scripts resolve poster dimensions, inventory reusable figures, lint print-day problems, and time spoken pitches.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    If the venue also gives a board limit, include it:

    line 45
  2. Distinctive:

    Prefer figures that are central to the paper's claim, cited often, and still readable when enlarged.

    line 57
  3. Distinctive:

    Keep the short pitch conversational.

    line 82
  4. Distinctive:

    Never invent venue size, board size, or print requirements.

    line 94
  5. Distinctive:

    Never alter data values, axes, or results to make a figure look better.

    line 95
  6. Distinctive:

    Do not reproduce third-party figures unless the user has rights to use them.

    line 96
  7. Distinctive:

    Keep posters readable from a distance: if text only fits at tiny sizes, cut it.

    line 97

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

Make Poster

Turn a paper or poster draft into a print-ready conference poster plan, with real dimensions, readable typography, figure reuse, and a timed short pitch. This skill is for posters and poster-session delivery; use make-slides for podium talks.

When to use

  • The user needs a research poster for a conference, workshop, demo session, or department event.
  • The venue gives a size such as A0, A1, 36x48in, 48x36in, or a custom board.
  • A LaTeX poster already exists and needs a print-day lint pass.
  • The user wants a 2-minute or 5-minute pitch for visitors.

Inputs

  • Poster size from presenter instructions or the acceptance email. Do not guess the board size from memory.
  • Optional: the paper's main .tex file, so figures can be inventoried and copied from the source tree.
  • Optional: existing poster source, usually beamerposter or tikzposter.
  • Optional: draft pitch text in markdown or plain text.

Process

  1. Confirm the physical size and orientation. Run:

    python3 scripts/poster_size.py --size 36x48in
    python3 scripts/poster_size.py --size a0 --orientation portrait

    If the venue also gives a board limit, include it:

    python3 scripts/poster_size.py --size 36x48in --board 48x96in
  2. Inventory paper figures when a LaTeX paper source is available:

    python3 scripts/poster_figures.py paper/main.tex --copy-to poster/assets

    Prefer figures that are central to the paper's claim, cited often, and still readable when enlarged. Avoid cramming full paper multi-panel figures onto the poster without simplification.

  3. Draft or revise the poster around a small number of claims. A good poster is not a paper pasted onto a board: use claim-style section headings, one hero visual, short method/evaluation blocks, and a clear takeaway with contact information or a QR code.
  4. Lint the poster source:

    python3 scripts/poster_lint.py poster/poster.tex --expect-size 36x48in

    Fix every RISK finding before sending to print. With --strict, warnings also fail the run.

  5. Time the pitch:

    python3 scripts/pitch_check.py poster/pitch-2min.md --minutes 2
    python3 scripts/pitch_check.py poster/pitch-5min.md --minutes 5

    Keep the short pitch conversational. It should end by inviting the visitor into the discussion rather than dumping every result.

Output

  • Exact poster dimensions and suggested LaTeX invocation.
  • Figure inventory and recommended hero-figure candidates.
  • Lint report with print-day risks and warnings.
  • A timed 2-minute or 5-minute pitch, or feedback on an existing pitch.

Guardrails

  • Never invent venue size, board size, or print requirements.
  • Never alter data values, axes, or results to make a figure look better.
  • Do not reproduce third-party figures unless the user has rights to use them.
  • Keep posters readable from a distance: if text only fits at tiny sizes, cut it.

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.