agentleFS
Sign inStart free
JunMA98JunMA98/Computer-science-claude-skills/skills/latex-posters/SKILL.md

latex-posters

Skill3 starsChanged 8 months agoMITView on GitHub

Create computer science research posters in LaTeX for conferences, thesis defenses, demos, and lab presentations. Use when converting a CS paper, benchmark result, system design, or project summary into a poster with strong layout, readable figures, and concise technical messaging.

14 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 4

    Distinctive

    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 CS poster workflows.

    line 8
  2. Distinctive:

    Do not paste paragraph-heavy paper text into a poster.

    line 29
  3. Distinctive:

    Use the existing templates when they help:

    line 33
  4. Very specific:

    If a shell review is useful, use scripts/review_poster.sh.

    line 45
  5. Distinctive:

    When the user asks for poster help without specifying format, return:

    line 58

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “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

LaTeX Posters

Use this skill for CS poster workflows. Optimize for architecture diagrams, benchmark highlights, readable tables, and fast comprehension in a noisy conference setting.

Poster Types

Handle cases such as:

  • conference poster based on a paper submission
  • lab or department poster for ongoing work
  • thesis or defense poster
  • demo poster for systems, agents, or tools
  • recruitment or project-overview poster for a research group

Content Strategy

A strong CS poster usually prioritizes:

  • problem and why it matters
  • core method or system architecture
  • benchmark setup or experimental protocol
  • 1 to 3 key result panels
  • limitations or deployment considerations
  • QR code or repo / paper link

Do not paste paragraph-heavy paper text into a poster. Compress aggressively.

Local Assets

Use the existing templates when they help:

  • assets/beamerposter_template.tex
  • assets/tikzposter_template.tex
  • assets/baposter_template.tex
  • assets/poster_quality_checklist.md

Read references selectively:

  • references/poster_content_guide.md
  • references/poster_design_principles.md
  • references/poster_layout_design.md
  • references/latex_poster_packages.md

If a shell review is useful, use scripts/review_poster.sh.

CS-Specific Review Checklist

Check that:

  • the title states the technical problem clearly
  • the method or system diagram is legible from distance
  • result panels show the main comparison immediately
  • figure captions carry the takeaway, not just labels
  • code, dataset, or paper links are easy to find

Default Output

When the user asks for poster help without specifying format, return:

  1. a poster outline
  2. a template recommendation
  3. section-level content priorities
  4. layout and readability risks

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.

Check your setup, free