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.
84
81%
Does it follow best practices?
Impact
Pending
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 narrow, specific niche (LaTeX academic poster creation) with concrete actions and explicit trigger guidance. It names specific packages (beamerposter, tikzposter, baposter) and use cases (conference or thesis posters), making it highly distinguishable. The 'Use when...' clause provides clear activation criteria.
| 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 domain well with both general and package-specific terms. | 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 writing skills, or other document creation skills due to the very specific domain. | 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 clear workflows, good refusal boundaries, and a sensible package decision matrix. Its main weaknesses are the lack of any executable LaTeX code examples (surprising for a LaTeX-focused skill) and moderate redundancy across sections. The content would benefit from concrete code snippets showing minimal working poster blocks for each package.
Suggestions
Add at least one minimal working LaTeX example per package (tikzposter, beamerposter, baposter) showing a basic block/column structure—even 5-10 lines each would dramatically improve actionability.
Consolidate the overlapping 'Core Deliverables', 'Writing Output Contract', and workflow step 5 into a single authoritative section to reduce redundancy and improve token efficiency.
Move the Package Decision Matrix and Academic Writing Rules into separate referenced files (e.g., assets/package_guide.md) to keep SKILL.md as a concise overview with clear pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some redundancy—the 'Core Deliverables' section overlaps significantly with the 'Writing Output Contract' and the workflow's step 5. The 'When to Use' / 'When Not to Use' sections explain things Claude could infer. Some tightening would improve token efficiency. | 2 / 3 |
Actionability | The skill provides structured guidance with clear section lists, word budgets, and a decision matrix, but lacks any executable LaTeX code examples. For a LaTeX-focused skill, at least a minimal working example of a tikzposter/beamerposter/baposter block structure would significantly improve actionability. The references to bundled assets partially compensate but the skill itself contains no concrete code. | 2 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with logical progression from context gathering through package selection, narrative compression, figure planning, and assembly. The refusal/recovery contract provides explicit error handling, and the final quality checklist serves as a validation checkpoint before delivery. | 3 / 3 |
Progressive Disclosure | The skill references bundled assets (templates and checklist) which is good progressive disclosure, but the main file itself is fairly long with content that could be split out (e.g., the package decision matrix, the writing output contract, or the academic writing rules could be separate reference files). The structure is decent but the SKILL.md tries to be both overview and complete reference. | 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 | |
8277276
Table of Contents
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.