baoyu-slide-deck
Generates professional slide deck images from content. Creates outlines with style instructions, then generates individual slide images. Use when user asks to "create slides", "make a presentation", "generate deck", "slide deck", or "PPT".
Install with Tessl CLI
npx tessl i github:jimliu/baoyu-skills --skill baoyu-slide-deckOverall
score
89%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
92%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 skill description that clearly communicates capabilities and includes explicit trigger guidance. The description uses proper third-person voice and provides good coverage of natural user terms. Minor improvement could be made by emphasizing the image-generation distinction more clearly to avoid conflicts with traditional presentation editing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Generates professional slide deck images', 'Creates outlines with style instructions', 'generates individual slide images'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (generates slide deck images, creates outlines with style instructions, generates individual slides) AND when (explicit 'Use when' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user terms: 'create slides', 'make a presentation', 'generate deck', 'slide deck', 'PPT'. These are exactly what users would naturally say when requesting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies 'slide deck images' which is somewhat distinct, there could be overlap with other presentation skills that work with .pptx files or presentation editing. The image-generation aspect helps differentiate but isn't strongly emphasized in the triggers. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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-crafted, highly actionable skill with excellent workflow clarity and progressive disclosure. The multi-step process is clearly sequenced with required checkpoints and conditional review steps. Minor verbosity in style tables and some redundancy between the checklist and flow diagram prevent a perfect conciseness score.
Suggestions
Move the detailed style presets table (16 presets) to a reference file and keep only 3-4 most common examples inline
Remove the duplicate workflow representation (checklist + flow diagram) - keep only the checklist which is more actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (workflow checklist duplicated with flow diagram, multiple tables repeating similar information). Some sections like the style presets table could be moved to references rather than inline. | 2 / 3 |
Actionability | Provides fully executable bash commands, specific file paths, concrete AskUserQuestion formats with exact options, and copy-paste ready code blocks. Every step has clear, specific instructions. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit checkpoints (⚠️ REQUIRED markers), conditional branching clearly documented, validation steps (Step 1.3 existing content check), and clear feedback loops for review cycles. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, detailed steps inline where needed, and appropriate references to external files (references/*.md) for detailed specs. Navigation table at end provides clear signposting to supplementary materials. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (695 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- 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.