القائمة
End-to-end PPT workflow skills for goal discovery, slide structure, slide writing, editable PPTX generation, final review, and presentation practice. Designed to be portable across Codex, Claude Code, and OpenClaw.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill after PPT slide writing is approved to build an editable PowerPoint/PPTX from PPT Project Brief v3. It routes into either the default SVG-native page-by-page design branch or the optional PPTGenJS template-native branch, applies playback/animation settings, runs build QA, and outputs PPT Project Brief v4: Built Deck.
Use this skill after ppt-deck-builder has produced a PPT delivery package. It acts as a final quality gate, not just a review report: it checks content, logic, copy, data/source, assets, compliance, visuals, layout, and delivery readiness; outputs PASS, FAIL, or CONDITIONAL_PASS; generates fix requests for the responsible prior skill; and only allows ppt-presentation-practice after PASS.
Use this skill whenever the user wants to start a PPT, PowerPoint, slide deck, report deck, proposal, pitch deck, training deck, course deck, or business presentation and needs help clarifying what the deck should achieve. This skill is not a questionnaire: it starts from the user's natural description and any uploaded materials, diagnoses the real job of the deck, asks one high-impact follow-up question at a time, and produces a Goal Diagnosis that prepares the next PPT workflow step.
Use this skill whenever the user wants to create, improve, generate, check, or rehearse a PPT, PowerPoint, slide deck, presentation, report deck, course deck, pitch deck, proposal deck, or business presentation. This is the router for the six-skill PPT workflow: ppt-goal-setting, ppt-slide-structure, ppt-slide-writing, ppt-deck-builder, ppt-final-check, and ppt-presentation-practice.
Use this skill after a PPT has been built and preferably final-checked. It helps the user rehearse and deliver the presentation by creating a speaking strategy, timing plan, slide-by-slide speaker cards, transitions, audience questions, pressure questions, answer strategies, and emergency talking points.
Use this skill after the presentation goal has been diagnosed, especially when the user needs a clear PPT structure, story flow, chapter plan, timing plan, or slide-by-slide skeleton. This skill chooses suitable thinking frameworks for the deck type, audience, goal, materials, delivery time, and desired experience, then turns them into a practical structure plan before slide copy is written.
| name | PPT-Maker |
| description | End-to-end PPT workflow skills for goal discovery, slide structure, slide writing, editable PPTX generation, final review, and presentation practice. Designed to be portable across Codex, Claude Code, and OpenClaw. |
| version | 0.1.0 |
Use this skill collection when the user wants to create, improve, review, or rehearse a PowerPoint/PPT deck through a structured workflow.
This repository contains a coordinated group of skills:
ppt-goal-setting - clarify PPT goal, audience, constraints, references, and success criteria.ppt-slide-structure - research the topic and choose a suitable scenario-specific structure.ppt-slide-writing - turn the approved structure into slide-level copy, layout intent, components, and image prompts.ppt-deck-builder - build an editable PPTX with TypeScript + PptxGenJS when the local runtime is available.ppt-final-check - review logic, language, facts, data, layout risks, and delivery readiness.ppt-presentation-practice - rehearse questions, objections, speaker notes, and response strategy.If the user asks for the whole process, start with skills/PPT-Maker/SKILL.md.
If the user asks for a specific phase, use the matching child skill directly.
Designed to be portable across Codex, Claude Code, and OpenClaw.
Text-only phases can run in any agent environment that supports local skills. PPTX generation requires Node.js and the included tools/ppt-builder-cli package.
The skills are the product. The TypeScript builder is only an optional execution tool used by ppt-deck-builder to generate editable .pptx files.
Do not assume platform-specific connectors, private memory files, absolute local paths, or proprietary image-generation tools. When image generation is unavailable, produce structured image prompts or placeholders and record the limitation.
For decks that need files, assets, rebuilds, or later review, use the lightweight project structure in references/project-structure.md.
Key project artifacts:
00-intake/user-brief.md00-intake/source-index.json01-research/research-brief.json02-structure/structure-plan.json03-production/slide-production-spec.json04-design/design-brief.json04-design/design-system.json04-design/template-selection.json05-build/deck-builder-input.json06-review/quality-report.json07-practice/practice-report.mdUse project mode for long decks, source-heavy decks, generated assets, or any deck that may need resume/rebuild cycles.
For new or rebuildable projects, keep Skill 3 and Skill 4 connected through stable protocol files:
references/v2-architecture.md defines the V2 artifact flow.references/source-intake.md defines source package and citation handling.references/research-brief.md defines the research brief.references/visual-component-registry.md defines components, icons, charts, and Mermaid usage.references/template-system-v2.md defines theme/layout/component/template layering.references/design-router.md defines how scenario, audience, goal, and mood become design parameters.references/design-brief.md defines the deck-level design decision contract.references/component-pack-registry.md defines reusable component pack choices.references/slide-spec.md defines 03-production/slide-production-spec.json.references/skill3-slide-spec-generation.md defines how Skill 3 should generate the contract from v2.references/layout-registry.md defines reusable layout IDs.references/theme-tokens.md defines the visual token system.Treat these files as the first phase of the architecture. They make the workflow portable across agent platforms and reduce model guesswork during PPTX generation.