CtrlK
BlogDocsLog inGet started
Tessl Logo

latex-posters

Creates academic-poster writing packages for LaTeX using beamerposter, tikzposter, or baposter. Use when a user needs poster-ready section copy, figure plans, captions, and package-specific layout decisions for conference or thesis posters.

65

Quality

78%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

72%

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

The body is concise and well-structured with good progressive disclosure and concrete budgets, but its actionability and workflow validation are held back by abstract LaTeX guidance and an unused bundled review script. Wiring the existing review_poster.sh into the workflow as a verification checkpoint would lift both dimensions.

Suggestions

Reference scripts/review_poster.sh explicitly as a validation step in the workflow so the bundled checker becomes a real verify gate.

Add a short concrete LaTeX snippet or template-wiring instruction (e.g., how to start from assets/tikzposter_template.tex) to make the assembly guidance executable rather than abstract.

DimensionReasoningScore

Conciseness

Lean body with no concept-explaining filler (no "what a poster is" padding) and every section earning its place; assumes Claude's competence throughout.

3 / 3

Actionability

Gives concrete budgets ("300-800 words", "5-6 blocks", "2-4 bullets"), a 7-item output contract, and a literal refusal template, but LaTeX assembly guidance stays abstract with no executable code or copy-paste commands.

2 / 3

Workflow Clarity

A clear 5-step sequenced workflow plus a final quality checklist exists, but validation is an implicit self-check rather than a hard verify gate, and the bundled scripts/review_poster.sh is never wired in as a checkpoint.

2 / 3

Progressive Disclosure

Overview points to real one-level-deep bundle assets (assets/*.tex, assets/poster_quality_checklist.md) as the implementation anchor, with content appropriately split and clearly signaled navigation.

3 / 3

Total

10

/

12

Passed

Description

85%

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, complete, and distinctive, with explicit "Use when..." triggers and named concrete deliverables. Its main weakness is relying on package-name jargon for trigger terms rather than plain user phrasing.

Suggestions

Add plain-language trigger terms users actually say (e.g., "research poster", "academic poster", "conference poster") alongside the package names.

Consider a short phrasing like "Use when a user needs a research or conference poster in LaTeX..." to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "poster-ready section copy", "figure plans", "captions", and "package-specific layout decisions" across three named packages — matching the multi-action anchor.

3 / 3

Completeness

Explicitly states what it does ("Creates academic-poster writing packages...") and gives an explicit "Use when a user needs..." trigger clause, answering both what and when.

3 / 3

Trigger Term Quality

Has relevant terms ("conference or thesis posters", "figure plans", "captions") but leans on technical package names (beamerposter/tikzposter/baposter) that many users would not say, and omits plain variations like "research poster".

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (LaTeX academic posters via three specific packages) with distinct triggers unlikely to collide with general document skills.

3 / 3

Total

11

/

12

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
aipoch/medical-research-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.