Use this skill any time the user wants to create a new PowerPoint presentation, slide deck, pitch deck, or .pptx file from scratch. Covers creating business presentations, quarterly reports, project proposals, product roadmaps, training materials, and any multi-slide document destined for PowerPoint. Works by generating HTML/CSS slides (which LLMs excel at), rendering them in agent-browser for pixel-accurate DOM position extraction, and assembling the final PPTX with native PowerPoint charts, tables, and images via PptxGenJS. Includes bundled scripts for validation, DOM extraction, and PPTX assembly. Do NOT use this skill for editing existing PPTX files, converting other formats to PPTX, or extracting content from PPTX files.
95
100%
Does it follow best practices?
Impact
76%
2.05xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 an excellent skill description that hits all the key criteria. It provides rich trigger terms covering natural user language, clearly states both what the skill does and when to use it, describes the technical implementation pipeline, and explicitly delineates boundaries to prevent conflicts with related skills. The inclusion of specific use cases (quarterly reports, pitch decks, etc.) and negative scope guidance makes it highly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and use cases: creating business presentations, quarterly reports, project proposals, product roadmaps, training materials. Also describes the technical pipeline (HTML/CSS rendering, DOM extraction, PPTX assembly with PptxGenJS). | 3 / 3 |
Completeness | Clearly answers both 'what' (create new PowerPoint presentations from scratch using HTML/CSS rendering pipeline) and 'when' (explicit 'Use this skill any time the user wants to create a new PowerPoint presentation...' trigger clause). Also includes explicit negative boundaries ('Do NOT use this skill for editing existing PPTX files...'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'PowerPoint presentation', 'slide deck', 'pitch deck', '.pptx file', 'business presentations', 'quarterly reports', 'project proposals', 'product roadmaps', 'training materials'. These are all terms users would naturally use when requesting this capability. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear boundaries. Explicitly scoped to creating new PPTX files from scratch, and explicitly excludes editing, converting, or extracting from existing PPTX files. The negative use-case guidance ('Do NOT use this skill for...') further reduces conflict risk with related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exceptionally well-crafted skill that handles a complex multi-step pipeline (HTML → browser rendering → DOM extraction → PPTX assembly) with remarkable clarity and precision. Every command is executable, validation checkpoints are explicit with feedback loops, and content is appropriately split between the overview and reference files. The troubleshooting table adds practical value without bloating the document.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude's competence with HTML/CSS, JavaScript, and CLI tools. The brief 'Why HTML?' justification earns its place by explaining the non-obvious architectural decision. No unnecessary explanations of basic concepts. | 3 / 3 |
Actionability | Every step includes exact, copy-paste-ready bash commands and code snippets. The pipeline is fully executable with specific viewport dimensions (960x540), exact file paths, concrete jq commands, and precise agent-browser CLI invocations. Placeholder HTML examples are complete and specific. | 3 / 3 |
Workflow Clarity | The 5-step pipeline is clearly sequenced with explicit validation checkpoints: Step 2 validates HTML and requires fixing errors before proceeding, Step 4 requires visual preview confirmation before PPTX assembly, and the troubleshooting table provides error recovery guidance. The feedback loop (validate → fix → re-validate) is explicit. | 3 / 3 |
Progressive Disclosure | The SKILL.md provides a clear overview with well-signaled one-level-deep references to three specific files (html-rules.md, slide-templates.md, pptxgenjs.md). Key constraints are summarized inline while detailed rules are deferred to reference files. The scripts table provides a clean index of all bundled tools. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
79bb9b8
Table of Contents
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.