agentsclimarketplace
Sign in

Make poster

Skill ShaishavMaisuria/research-paper-lifecycle-skills/skills/make-poster

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.From its SKILL.md

Install
npx -y skills add ShaishavMaisuria/research-paper-lifecycle-skills --skill make-poster

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 23 stars23 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 7 commands, including `python3 scripts/poster_size.py --size 36x48in` and 6 more.

SKILL.md

3.4 KB, 723 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it: 4 files

40.0 KB alongside SKILL.md, 4 of them executable

scripts/

Gives 0 of the 12 instructions most quality gates skills give in 723 tokens

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

  • Read full output and check exit codein 45 of 1524, across 40 files
  • Verify output confirms the claimin 44 of 1524, across 39 files
  • Identify the command that proves the claimin 43 of 1524, across 39 files
  • Execute the full verification commandin 36 of 1524, across 30 files
  • Produce a verification reportin 34 of 1524, across 18 files
  • Review git diff changesin 30 of 1524, across 16 files
  • Fix build failures immediatelyin 29 of 1524, across 9 files
  • Group findings by severityin 28 of 1524
  • State claim only with evidencein 27 of 1524, across 22 files
  • Verify regression tests with red-green cyclein 26 of 1524, across 22 files
  • Run the full test suitein 26 of 1524, across 25 files
  • Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

  • Confirm physical size and orientation
  • Inventory paper figures for reuse
  • Draft poster using claim-style headings
  • Lint poster source for print risks
  • Fix all identified print risks
  • Time the poster pitch

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.