pptx-posters
Generate PowerPoint presentations and academic posters from paper content
55
35%
Does it follow best practices?
Impact
90%
3.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/Academic Writing/pptx-posters/SKILL.mdQuality
Discovery
32%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 identifies a clear use case (converting academic papers to presentations/posters) but lacks explicit trigger guidance and comprehensive action verbs. It would benefit from a 'Use when...' clause and more natural user keywords to help Claude reliably select this skill from a large skill library.
Suggestions
Add a 'Use when...' clause with trigger terms like 'convert paper to slides', 'create conference poster', 'research presentation', 'paper summary slides'
Include file format keywords users might mention: '.pptx', 'slides', 'poster', 'conference presentation'
Expand specific actions: 'extracts key findings, creates slide layouts, formats figures and citations'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (PowerPoint presentations, academic posters) and mentions 'paper content' as input, but doesn't list comprehensive actions like 'create slides', 'format layouts', 'add figures', etc. | 2 / 3 |
Completeness | Describes what it does (generate presentations/posters from papers) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some natural terms like 'PowerPoint presentations' and 'academic posters', but missing common variations like '.pptx', 'slides', 'conference poster', 'research presentation', or 'paper to slides'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'academic posters' and 'paper content' provides some distinctiveness, but 'PowerPoint presentations' is generic enough to potentially conflict with general presentation skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides basic CLI usage but is padded with extensive boilerplate sections (risk assessment, security checklist, evaluation criteria, lifecycle status) that consume tokens without helping Claude perform the task. The core functionality is underspecified - there's no guidance on handling failures, customizing output, or understanding what the scripts actually do.
Suggestions
Remove or relocate boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) to a separate metadata file or eliminate entirely
Add a workflow with validation steps: generate → review output → iterate if needed, with specific guidance on common issues
Include concrete examples of template customization or show sample output structure to make the skill more actionable
Add troubleshooting guidance for common failures (malformed PDF, missing sections, layout issues)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes unnecessary boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that add significant token overhead without providing actionable guidance for the task. The core content is reasonably concise but buried under administrative cruft. | 2 / 3 |
Actionability | Provides CLI usage examples which are concrete, but lacks any actual implementation details, code examples for customization, or guidance on what the scripts do internally. The 'Features' section describes capabilities abstractly rather than showing how to use them. | 2 / 3 |
Workflow Clarity | No workflow is defined beyond running a single command. There's no guidance on what to do if generation fails, how to iterate on output quality, or how to handle common issues like missing figures or malformed input. For a document generation task, validation steps are notably absent. | 1 / 3 |
Progressive Disclosure | Content is organized into sections but includes too much inline boilerplate that should either be removed or moved to separate files. No references to additional documentation for templates, advanced customization, or troubleshooting. | 2 / 3 |
Total | 7 / 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
4a48721
- 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.