ppt-creator▌
daymade/claude-code-skills · updated May 12, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Transform topics or documents into persuasive, data-driven slide decks with speaker notes and PPTX export.
- ›Applies Pyramid Principle and assertion-evidence storytelling to structure content with one core conclusion supported by 3-5 reasons and evidence
- ›Generates complete deliverables: structured Markdown slides, speaker notes (45-60 seconds per slide), charts, citations, and optional PPTX files
- ›Includes built-in chart selection guidance, accessibility compliance (WCAG AA), and self-s
PPT Creator
Goal: Transform a simple topic into a presentation-ready, high-quality slide deck. When key information is missing, use the minimal intake form (references/INTAKE.md) to gather context or apply safe defaults. Then follow the workflow (references/WORKFLOW.md) to produce an outline, slide drafts, charts, and speaker notes. After generation, self-evaluate using the rubric (references/RUBRIC.md); if the score is < 75, automatically refine up to 2 iterations until ≥ 75 before delivery. See Deliverables section for final output structure.
When to Use This Skill
Use this skill when the user requests:
- "Make a presentation/deck/PPT/slides" on any topic
- "Improve/optimize a presentation/pitch/demo"
- Converting scattered materials into a structured, persuasive slide deck
- Creating presentations with data visualization and speaker notes
- Building decks for business reviews, product pitches, educational content, or reports
Quick Start
-
Gather Intent: If critical information is missing, ask the 10 Minimal Questions (references/INTAKE.md). If the user doesn't respond after 2 prompts, use the safe default for each item and clearly note assumptions in speaker notes.
-
Structure the Story: Apply the Pyramid Principle to establish "one conclusion → 3-5 top-level reasons → supporting evidence." Each slide uses assertion-style headings (complete sentences), with body content providing evidence (charts/tables/diagrams/data points). Templates are in references/TEMPLATES.md.
-
Choose Charts: Use the Chart Selection Dictionary in references/VIS-GUIDE.md to pick the most appropriate visualization for each point. If the user provides data (tables/CSV), optionally call
scripts/chartkit.pyto generate PNG charts; otherwise, create placeholder diagrams with a list of required data fields. -
Layout & Style: Follow references/STYLE-GUIDE.md for font sizes, line spacing, white space, contrast ratios, color palettes, and accessibility (WCAG AA compliance).
-
Speaker Notes: Generate 45-60 second speaker notes for each slide, structured as: opening → core assertion → evidence explanation → transition.
-
Self-Check & Score: Use references/CHECKLIST.md for a pre-flight check, then score with references/RUBRIC.md. If total score < 75, identify the weakest 3 items and refine; repeat scoring (max 2 iterations).
-
Deliverables (all saved to
/output/):/output/slides.md: Markdown slides (Marp/Reveal.js compatible), with assertion-style headings + bullet points/chart placeholders + notes/output/assets/*.png: Generated charts (if applicable)/output/notes.md: Full speaker notes and delivery outline/output/refs.md: Citations and data sources/output/presentation.pptx: Ifpython-pptxis available, export to PPTX; otherwise, keep Markdown and include instructions for "one-click conversion to PPTX" in the first screen (does not block delivery)
Orchestration Mode (End-to-End Automation)
When the user requests a "complete" or "presentation-ready" deliverable, ppt-creator automatically orchestrates the full pipeline: content creation → data synthesis → chart generation → dual-path PPTX creation (Marp + document-skills:pptx) → chart insertion. This typically delivers TWO complete PPTX files with different styling for user comparison.
Activation: Phrases like "complete PPTX", "final deliverable", "ready for presentation" Duration: 4-6 minutes (parallel execution) Output: presentation_marp_with_charts.pptx + presentation_pptx_with_charts.pptx
For orchestration details, see references/ORCHESTRATION_OVERVIEW.md (start here), then navigate to specialized guides as needed.
Core Principles (Must Follow)
- Information Organization: Conclusion first, then evidence (Pyramid Principle). Each slide conveys only 1 core idea. Headings must be testable assertion sentences, not topic labels.
- Evidence-First: Use charts/tables/evidence blocks instead of long paragraphs; limit to 3-5 bullet points per slide.
- Data Visualization: Chart selection and labeling (axes/units/sources) must comply with references/VIS-GUIDE.md. If data is insufficient, provide "placeholder chart + list of missing fields."
- Accessibility: Color and text contrast must meet AA standards (see STYLE-GUIDE). Provide alt/readable descriptions for charts and images.
- Reusability: Use consistent naming, stable paths, reproducible output. Do not hard-code random numbers in code.
- Safety & Dependencies: Do not scrape the web without permission. Only run scripts when user provides data. If
matplotlib/pandasare unavailable, fall back to text + placeholder diagram instructions.
Workflow Overview
Stage 0 - Archive Input: Record user's original request, defaults used, and assumptions made.
Stage 1 - Structure Goals: Rewrite the goal into "who takes what action when" (clear CTA).
Stage 2 - Storyline: Use Pyramid Principle to define "one-sentence conclusion → 3-5 first-level reasons → evidence."
Stage 3 - Outline & Slide Titles: Create a 12-15 slide chapter skeleton. Each slide has one assertion-style heading.
Stage 4 - Evidence & Charts: Use the Chart Selection Dictionary from VIS-GUIDE. If data is provided, call chartkit.py to generate PNGs; otherwise, create placeholder + required field list.
Stage 5 - Layout & Accessibility: Apply STYLE-GUIDE for font sizes, spacing, contrast ratios, color palettes; unify units and decimal places.
Stage 6 - Speaker Notes: Generate 45-60 second notes per slide: opening → assertion → evidence explanation → transition.
Stage 7 - Self-Check & Scoring: Run CHECKLIST; score with RUBRIC. If score < 75, focus on weakest 3 items, refine, re-score (max 2 iterations).
Stage 8 - Package Deliverables: Generate /output/ directory with slides.md / notes.md / refs.md / assets/*.png. If python-pptx is available, export PPTX.
Stage 9 - Reuse Instructions: Append a "5-step guide to replace data/colors with your own" at the end of notes.md.
Resources
references/INTAKE.md
Minimal 10-Item Questionnaire (use defaults if missing):
- Who is the audience? (Default: general public)
- Core objective? (Default: "understand and accept" a proposition)
- Desired action/decision? (Default: agree to move to next step after the meeting)
- Duration & slide count limit? (Default: 15-20 min, 12-15 slides)
- Tone & style? (Default: professional, clear, friendly)
- Topic scope & boundaries? (Default: given topic + 1 layer related)
- Must-include points/taboos? (Default: none)
- Available data/tables? (Default: none; can generate structure placeholder + list required fields)
- Brand & visual constraints? (Default: built-in neutral theme)
- Deliverable format preference? (Default: slides.md + optional PNG charts; export PPTX if available)
references/WORKFLOW.md
Detailed step-by-step process from "topic" to "presentation-ready output."
references/TEMPLATES.md
Slide Template Library (assertion-evidence style):
- Cover, Table of Contents, Problem Statement, Opportunity/Goal, Solution Overview, Evidence 1-3, Risk & Mitigation, Case Study/Comparison, Roadmap/Timeline, Conclusion & Actions, Backup Slides
- Micro-templates: Comparison (A vs B), Pyramid Summary, Process 4-Step, KPI Dashboard, Geographic Distribution, Funnel, Pareto, Sensitivity, Cost Structure (Waterfall), Contribution (Stacked)
references/VIS-GUIDE.md
Data Visualization Selection & Labeling Standards:
- Chart Selection Dictionary (common questions → chart types)
- Labeling & units (axes, units, data scope, time range; source in footer)
- Accessibility & contrast (WCAG 2.1 AA: text vs background ≥ 4.5:1; UI elements ≥ 3:1)
- Assertion-Evidence writing tips
references/STYLE-GUIDE.md
Layout & Style (neutral theme, supports brand replacement):
- Canvas: 16:9; safe margins ≥ 48px; grid column spacing 24px
- Fonts: Chinese (Source Han Sans/PingFang/Hiragino Sans), English (Inter/Calibri)
- Font sizes: Heading 34-40, Subheading 24-28, Body 18-22, Footer 14-16
- Line spacing: Heading 1.1, Body 1.3; bullet spacing ≥ 8px
- Color palette (AA compliant): Dark ink #1F2937 / Background #FFFFFF / Accent #2563EB / Emphasis #DC2626
- Components: unified 6-8px border radius; charts and images with 8px padding
- Images: add brief alt descriptions for screen readers
- Page density: ≤ 70 words per slide (excluding captions)
references/RUBRIC.md
PPT Quality Scoring Rubric (100 points; ≥ 75 to deliver): Each item scored 0-10:
- Goal Clarity: Audience, objective, CTA well-defined
- Story Structure: Pyramid structure complete, hierarchy clear
- Slide Assertions: Headings are "assertion sentences" supported by evidence
- Evidence Quality: Data/cases/citations sufficient, credible, consistent calibration
- Chart Fit: Correct selection, complete labeling, readable
- Visual & Accessibility: Contrast, font size, white space, color compliance
- Coherence & Transitions: Natural chapter and page transitions
- Speakability: 45-60 sec per slide, natural language
- Deliverables Complete: slides.md / notes.md / refs.md / (optional) assets/*.png
- Robustness: Gaps explicitly marked, fallback plan & next steps provided
Self-evaluation process: Run CHECKLIST first, then score each item and write top 3 low-scoring items + improvement actions. If total < 75, apply actions and re-score (max 2 iterations).
references/CHECKLIST.md
Pre-flight checklist for final quality assurance before delivery.
references/EXAMPLES.md
Two Usage Examples:
- Example A: Ultra-simple topic ("coffee") → trigger minimal questionnaire, generate 12-page framework with placeholder charts
- Example B: Small business monthly review with attached CSV → parse data, select charts per VIS-GUIDE, call chartkit.py, refine 1-2 iterations if score < 75
scripts/chartkit.py
Minimal chart renderer for ppt-creator.
Usage:
python scripts/chartkit.py \
--data path/to/data.csv \
--type line \
--x date \
--y sales profit \
--out output/assets \
--filename kpi_trend.png \
--title "Monthly KPIs"
Notes:
- Requires:
pandas,matplotlib - Fallback: If packages unavailable, print instruction message and exit(0)
- Uses matplotlib defaults for readability (no hard-coded brand colors)
Advanced Tips
- This skill complements (not conflicts with) Anthropic's built-in PowerPoint generation capabilities. Use this skill to produce "high-quality structure & content," then optionally invoke system capabilities to export the final PPTX file.
- For complex data analysis needs, combine with other skills (e.g., data analysis, charting) before invoking ppt-creator.
- The skill is designed to be forgiving: missing information triggers safe defaults rather than blocking progress.
How to use ppt-creator on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add ppt-creator
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches ppt-creator from GitHub repository daymade/claude-code-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate ppt-creator. Access the skill through slash commands (e.g., /ppt-creator) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★64 reviews- ★★★★★Zaid Jain· Dec 28, 2024
ppt-creator has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ganesh Mohane· Dec 20, 2024
Useful defaults in ppt-creator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Zaid Kapoor· Dec 16, 2024
I recommend ppt-creator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Benjamin Li· Dec 12, 2024
Solid pick for teams standardizing on skills: ppt-creator is focused, and the summary matches what you get after install.
- ★★★★★Kofi Srinivasan· Dec 4, 2024
ppt-creator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Isabella Kim· Nov 23, 2024
ppt-creator reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Isabella Thompson· Nov 19, 2024
Useful defaults in ppt-creator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Zaid Rahman· Nov 15, 2024
We added ppt-creator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Rahul Santra· Nov 11, 2024
ppt-creator has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Aisha Srinivasan· Nov 7, 2024
Solid pick for teams standardizing on skills: ppt-creator is focused, and the summary matches what you get after install.
showing 1-10 of 64