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.
67
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly defines a specific niche (LaTeX academic poster creation), lists concrete deliverables, names specific packages, and includes an explicit 'Use when' clause with natural trigger terms. It effectively distinguishes itself from broader LaTeX or design skills through its specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'poster-ready section copy, figure plans, captions, and package-specific layout decisions.' Also names specific LaTeX packages (beamerposter, tikzposter, baposter). | 3 / 3 |
Completeness | Clearly answers both what ('Creates academic-poster writing packages... poster-ready section copy, figure plans, captions, and package-specific layout decisions') and when ('Use when a user needs poster-ready section copy... for conference or thesis posters'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'academic poster', 'LaTeX', 'beamerposter', 'tikzposter', 'baposter', 'conference poster', 'thesis poster', 'captions', 'layout'. These cover the main terms a user seeking this skill would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: academic poster creation specifically for LaTeX using named packages. Unlikely to conflict with general LaTeX skills, general poster design skills, or other document creation skills due to the specific combination of domain and tools. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured instructional skill with a clear workflow and good constraint definitions, but it lacks executable LaTeX examples which limits its actionability for a LaTeX-focused skill. The content is moderately concise but includes some sections that explain things Claude already knows. The referenced bundle assets would improve progressive disclosure but are missing.
Suggestions
Add at least one minimal working LaTeX example per package (beamerposter, tikzposter, baposter) showing a basic poster skeleton with 2-3 blocks, so Claude has copy-paste-ready starting points.
Provide the referenced bundle files (assets/tikzposter_template.tex, etc.) or remove references to them to avoid hallucination of nonexistent assets.
Remove or condense the 'When to Use / When Not to Use' and 'Academic Writing Rules' sections — Claude already knows conference-appropriate tone and can infer applicability from the skill description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some unnecessary sections like 'When to Use' and 'When Not to Use' that Claude can infer, and the 'Academic Writing Rules' section states things Claude already knows (neutral tone, grounded in evidence). The content could be tightened by ~30%. | 2 / 3 |
Actionability | The skill provides structured guidance with clear deliverables, word budgets, and a decision matrix, but lacks any executable LaTeX code examples. For a LaTeX poster skill, at least a minimal working example of each package would significantly improve actionability. The references to bundled template assets partially compensate, but those files aren't provided. | 2 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit steps: collect context → choose package → compress narrative → plan figures → assemble package. The refusal/recovery contract and final quality checklist serve as validation checkpoints. The workflow is well-suited to the non-destructive nature of the task. | 3 / 3 |
Progressive Disclosure | The skill references bundled assets (template files, quality checklist) which would provide good progressive disclosure, but none of these files are actually provided in the bundle. The SKILL.md itself is somewhat monolithic with all content inline rather than splitting detailed guidance (e.g., the package decision matrix, writing rules) into separate referenced files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- aipoch/medical-research-skills
- Commit
73f6514
- 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.