CtrlK
BlogDocsLog inGet started
Tessl Logo

latex-posters

Create professional research posters in LaTeX using beamerposter, tikzposter, or baposter. Support for conference presentations, academic posters, and scientific communication. Includes layout design, color schemes, multi-column formats, figure integration, and poster-specific best practices for visual communication.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/latex-posters/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, actionable guide with an explicit multi-stage workflow and strong validation gates, and it uses progressive disclosure effectively with real bundle files. Its main weakness is redundancy: the same graphic limits and overflow guidance are restated across multiple sections, inflating token usage without adding information.

Suggestions

De-duplicate the graphic limits: keep one authoritative table and have Stage 2 reference it instead of restating slightly different numbers (3-4 vs 4-5 elements, 10 vs 15 words).

Consolidate 'Common Pitfalls', 'Fixing Overflow', and 'Best Practices' into a single checklist to remove repeated guidance.

Trim concept-level framing (e.g. 'Research posters are a critical medium for scientific communication...') that assumes context Claude already has.

DimensionReasoningScore

Conciseness

The body is mostly efficient but repeats the same constraints twice — a 'Hard limits' table (3-4 elements, 10 words) and then Stage 2 'Content limits' (4-5 elements, 15 words) — and re-states the same overflow/pitfall guidance across 'Common Pitfalls' and 'Best Practices'; this redundant padding keeps it at 'mostly efficient but some unnecessary explanation could be tightened' rather than the lean score-4 anchor.

3 / 5

Actionability

It provides concrete, mostly copy-paste-ready commands and prompts (mkdir -p figures, the generate_schematic.py invocations with exact pt sizes, pdflatex/lualatex, tlmgr install) covering common cases, with only minor gaps (no template-loading example), matching 'mostly executable guidance; concrete code with minor gaps.'

4 / 5

Workflow Clarity

The six-stage workflow is clearly sequenced with explicit validation checkpoints and feedback loops — two mandatory review gates ('Before generating', 'After generating'), overflow checks via 'grep -i overfull poster.log', and a regenerate/split loop on failure — matching the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor.

5 / 5

Progressive Disclosure

SKILL.md serves as a clear overview pointing to well-signaled one-level-deep references (eight references/ files, three templates in assets/, scripts in scripts/, all verified to exist), with content appropriately split and easy navigation, matching the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

17

/

20

Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and well-differentiated with concrete capabilities and natural trigger terms, but it omits an explicit 'Use when...' guidance clause, which caps its completeness. Adding explicit invocation triggers would lift it to the top tier.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when creating research posters for conferences, poster sessions, thesis defenses, or converting papers to poster format.'

Include a few more natural synonyms and file extensions (e.g. .tex, poster session, symposium) to broaden trigger-term coverage.

Tighten 'poster-specific best practices for visual communication' to a concrete action verb to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

The description names the domain and lists several concrete capabilities — "layout design, color schemes, multi-column formats, figure integration" plus "poster-specific best practices" — giving good coverage with only minor gaps, which matches the 'several specific actions; minor gaps' anchor rather than the fully comprehensive score-5 example.

4 / 5

Completeness

It clearly answers 'what' (create professional research posters in LaTeX with listed features) but lacks any explicit 'Use when...' trigger clause; per the rubric a missing 'Use when...' clause caps completeness at 3, and it is not below 3 since the 'what' is clear and concrete.

3 / 5

Trigger Term Quality

Natural terms a user would say are well covered ("research posters", "academic posters", "conference presentations", plus size triggers "A0, A1, 36×48"), but a few synonyms/extensions are missing (e.g. .tex, poster session), placing it at 'good keyword coverage; a few natural terms missing' rather than the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — LaTeX research posters via beamerposter/tikzposter/baposter for conferences and academic events — with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
K-Dense-AI/scientific-agent-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.