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".
88
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 strong description that clearly communicates what the skill does and when to use it. It includes specific actions and natural trigger terms. The only weakness is potential overlap with other presentation-related skills, where the distinction of generating slide *images* versus editing .pptx files could be made more explicit.
Suggestions
Clarify the distinction from .pptx editing skills by emphasizing that this generates slide images (e.g., PNG/JPG) rather than editable presentation files, to reduce conflict risk with PowerPoint-focused skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: generates 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 professional slide deck images, creates outlines with style instructions, generates individual slide images) and 'when' (explicit 'Use when' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms users would actually say: 'create slides', 'make a presentation', 'generate deck', 'slide deck', 'PPT'. Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies slide deck *images* which is somewhat distinctive, it could overlap with a presentation editing/creation skill that works with .pptx files. The term 'presentation' and 'PPT' could trigger conflicts with a PowerPoint-focused skill. The image-generation approach is a differentiator but could be clearer. | 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, comprehensive skill for a complex multi-step workflow. Its greatest strengths are the exceptionally clear workflow with validation checkpoints, hard confirmation gates, and excellent progressive disclosure through well-organized reference files. The main weakness is verbosity — at this length, some sections (like the full 17-preset table and the detailed image backend resolution logic) could be moved to reference files to reduce token consumption in the main skill.
Suggestions
Move the 17-preset table and auto-selection signal table to a reference file (e.g., references/presets-overview.md) and keep only 3-4 example presets inline to reduce token usage in the main skill.
Consolidate the 'User Input Tools' and 'Image Generation Tools' sections — the tool-resolution logic is verbose and could be tightened to bullet-point rules rather than multi-paragraph explanations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~400+ lines) with substantial detail. While most content is necessary for a complex multi-step workflow, there's some redundancy (e.g., the confirmation policy is stated multiple times, the image backend resolution logic is verbose, and the 17-preset table could be a reference file). Some sections like 'User Input Tools' explain tool-selection logic that could be more concise. | 2 / 3 |
Actionability | The skill provides highly concrete, executable guidance: specific CLI commands for merging, exact file paths and naming conventions, detailed YAML frontmatter examples for references, precise workflow steps with clear branching logic, and specific flag names (--regenerate, --outline-only, etc.). The merge commands are copy-paste ready and the file layout is explicit. | 3 / 3 |
Workflow Clarity | The 9-step workflow is exceptionally well-structured with a checklist, explicit hard gates (Step 2 confirmation is marked ⚠️ REQUIRED), conditional steps clearly labeled, feedback loops (edit → re-validate → regenerate), backup rules for destructive operations, and auto-retry on failure. The confirmation policy prevents premature execution, and modification workflows include renumbering and re-merge steps. | 3 / 3 |
Progressive Disclosure | The skill masterfully uses progressive disclosure with a clear references table pointing to 12+ separate files for detailed specs (styles, dimensions, confirmation copy, analysis framework, etc.). All references are one level deep and clearly signaled. The main SKILL.md serves as an effective overview and orchestration guide while delegating detailed content appropriately. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- jimliu/baoyu-skills
- Commit
505a7e1
- 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.