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 solid description that excels at completeness and distinctiveness by explicitly defining when to use this skill versus the alternative (latex-posters). The trigger terms are well-chosen and cover natural user language. The main weakness is that the specificity of concrete actions could be stronger—the last sentence about 'modern web-based poster design with responsive layouts' reads as marketing fluff rather than actionable capability description.
Suggestions
Replace the vague closing sentence ('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, PDF, and PPTX export, but doesn't list multiple 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' (explicitly states 'Use this skill ONLY when the user explicitly requests PowerPoint/PPTX poster format' and distinguishes from latex-posters). The explicit trigger guidance is well-defined. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'research posters', 'HTML/CSS', 'PDF', 'PPTX', 'PowerPoint', 'poster format'. These cover common variations a user would naturally say when requesting this type of work. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly differentiates itself from the latex-posters skill by specifying when to use this skill vs. the other. The PPTX/PowerPoint trigger and HTML/CSS approach create a clear niche that is unlikely to conflict with other skills. | 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 highly actionable, concrete guidance with executable code examples and a well-structured multi-stage workflow with validation checkpoints. However, it is severely bloated with repetitive content—the font size requirements, simplification rules, and element count limits are stated 3-4 times across different sections. The inline content significantly overlaps with referenced external files (quality checklist, design principles), undermining the progressive disclosure structure.
Suggestions
Consolidate the repeated font size/simplification/white space requirements into a single authoritative section, and reference it from other sections rather than restating it each time.
Move the detailed Quality Checklist content to the referenced poster_quality_checklist.md file and keep only a brief summary with a link in SKILL.md.
Remove the 'When to Use / When Not to Use' section or reduce it to 1-2 lines—the YAML description already covers this, and Claude can infer routing logic from a brief note.
Cut the 'Common Pitfalls' section which largely restates rules already covered in the Quality Checklist and visual generation sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines with significant repetition. The font size requirements, content overflow rules, and simplification guidelines are repeated multiple times across sections (AI-Powered Visual Element Generation, Generating Visual Elements, Quality Checklist, Common Pitfalls). The 'When to Use' section is overly detailed for something Claude can infer. Many sections explain obvious concepts (what HTML/CSS posters are, what a three-column layout looks like). | 1 / 3 |
Actionability | The skill provides fully executable code examples throughout: bash commands for generating schematics, Chrome headless PDF export commands, python-pptx code for direct PPTX creation, HTML/CSS snippets with specific class names and font sizes. The template copy command and directory structure are concrete and copy-paste ready. | 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 (poster_html_template.html, poster_quality_checklist.md, poster_content_guide.md, poster_design_principles.md, poster_layout_design.md) which is good structure, but the SKILL.md itself is monolithic with massive inline content that duplicates what should be in those reference files. The quality checklist content is inline despite a separate poster_quality_checklist.md existing. No bundle files were provided to verify references exist. | 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
cbcae7b
- 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.