pptx-posters
Create research posters using HTML/CSS that can be exported to PDF or PPTX. Use this skill ONLY when the user explicitly requests PowerPoint/PPTX poster format. For standard research posters, use latex-posters instead. This skill provides modern web-based poster design with responsive layouts and easy visual integration.
80
76%
Does it follow best practices?
Impact
83%
1.48xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/pptx-posters/SKILL.mdQuality
Discovery
89%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 well-crafted description that excels at completeness and distinctiveness, with explicit trigger conditions and clear disambiguation from a related skill. The trigger terms are strong and natural. The main weakness is that the specificity of concrete actions could be improved — it mostly says 'create' and 'export' without detailing specific capabilities, and the closing phrase about 'modern web-based poster design with responsive layouts' reads as marketing fluff rather than concrete functionality.
Suggestions
Replace the vague closing phrase ('modern web-based poster design with responsive layouts and easy visual integration') with specific concrete actions, e.g., 'Supports custom layouts, image placement, chart embedding, and multi-column designs.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (research posters) and mentions HTML/CSS creation with export to PDF/PPTX, but doesn't list multiple specific concrete actions beyond 'create' and 'export'. Phrases like 'modern web-based poster design with responsive layouts and easy visual integration' are somewhat vague/fluffy. | 2 / 3 |
Completeness | Clearly answers both 'what' (create research posters using HTML/CSS exportable to PDF/PPTX) and 'when' (ONLY when user explicitly requests PowerPoint/PPTX poster format), with explicit trigger guidance and even a disambiguation clause pointing to latex-posters for standard cases. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'research posters', 'HTML/CSS', 'PDF', 'PPTX', 'PowerPoint', 'poster format', 'web-based poster'. These cover terms users would naturally use when requesting this type of work. | 3 / 3 |
Distinctiveness Conflict Risk | Excellent distinctiveness — explicitly differentiates itself from the latex-posters skill by specifying this is for PowerPoint/PPTX poster format only, and uses HTML/CSS approach. The disambiguation clause ('For standard research posters, use latex-posters instead') directly reduces conflict risk. | 3 / 3 |
Total | 11 / 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.
The skill provides excellent actionability with concrete, executable examples and a well-structured multi-stage workflow with validation checkpoints. However, it suffers significantly from verbosity and repetition—the same core rules about poster graphic simplicity (3-4 elements, 50% white space, giant fonts) are restated at least 5 times across different sections. The content would benefit greatly from consolidation and moving detailed checklists/pitfalls to referenced files.
Suggestions
Consolidate the repeated graphic simplicity rules (3-4 elements, 50% white space, giant fonts) into a single authoritative section, and reference it from other sections instead of restating it each time.
Move the detailed Quality Checklist and Common Pitfalls sections to the referenced `poster_quality_checklist.md` file, keeping only a brief summary with a link in the main SKILL.md.
Remove the 'When to Use / When Not to Use' section's redundancy with the overview warning—combine into a single concise routing directive at the top.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines. There is massive repetition of the same font size/simplicity rules across multiple sections (AI-Powered Visual Element Generation, Generating Visual Elements, Quality Checklist pre-generation, Quality Checklist post-generation, Common Pitfalls). The same '3-4 elements max, 50% white space, GIANT text' message is repeated at least 5 times. The 'When to Use' section also heavily overlaps with the overview warning. | 1 / 3 |
Actionability | The skill provides fully executable commands throughout: bash commands for generating schematics, Chrome headless PDF export commands, python-pptx code for direct PPTX creation, HTML/CSS snippets with specific values, and concrete template file paths. Examples are copy-paste ready with clear before/after patterns. | 3 / 3 |
Workflow Clarity | The 5-stage workflow (Planning → Generate Visuals → Create HTML → Export PDF → Convert PPTX) is clearly sequenced with explicit validation checkpoints. The quality checklist includes mandatory pre-generation review, post-generation review with pass/fail criteria, and post-export verification. Feedback loops are present (fail → regenerate with specific fixes). | 3 / 3 |
Progressive Disclosure | The skill references external files appropriately (template in assets/, references/ directory with design principles and content guides), but the main SKILL.md itself is a monolithic wall of content. Much of the detailed graphic generation guidance, quality checklists, and common pitfalls could be split into referenced files. The inline content is far too long for an overview document. | 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- K-Dense-AI/claude-scientific-skills
- Commit
b58ad7e
- 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.