presentation-builder
Base consulting PowerPoint generation skill. Use when the user asks for a PPT, presentation deck, executive briefing, proposal, project update, workshop material, roadmap deck, review deck, or client-ready slide deliverable. Provides reusable storyline presets and template guidance for strategy, proposal, and project-update decks.
guoliang1114-boop · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add guoliang1114-boop/AriaAI --skill presentation-builder技能说明
name: presentation-builder description: "Base consulting PowerPoint generation skill. Use when the user asks for a PPT, presentation deck, executive briefing, proposal, project update, workshop material, roadmap deck, review deck, or client-ready slide deliverable. Provides reusable storyline presets and template guidance for strategy, proposal, and project-update decks." version: "1.0.0" domain: "tech" last_updated: "2026-08-26" status: "stable"
Presentation Builder
This is the base Skill for consulting-style PowerPoint deliverables. It turns rough content, project context, client notes, or strategic analysis into a structured, editable PPT deck.
It is distilled from the stabilized digital-strategy PPT generation pattern: template-first rendering, chapter dividers, action-oriented titles, one-sentence page leads, rich body content, and management-grade evidence/action layers.
When To Use
Use this Skill for:
- Executive briefings
- Strategy decks
- Client proposals
- Project update decks
- Steering committee materials
- Workshop decks
- Roadmap or implementation plans
- Review and retrospective decks
If the request is specifically about digital transformation strategy, use digital-strategy for the strategy content and this Skill's PPT standards as the presentation layer.
Workflow
- Clarify the decision purpose and audience.
- Select a deck preset:
strategy,proposal, orproject-update. - Build a slide-by-slide storyline before calling the PPT tool.
- Use action-oriented slide titles.
- Fill each slide with enough evidence, assumptions, implications, and next actions for management discussion.
- For every business page, include four layers: conclusion, evidence/assumption, management action, and risk/trade-off/decision.
- Call
generate_ppt_from_skillwithskill_name: "presentation-builder".
Page Format Rules
Use slide types intentionally:
title: chapter divider or major transition page, not a normal content page.content: one clear argument with 4-6 bullets. Use for executive answer, context, findings, recommendations, risks, and decisions.two_column: comparison pages such as current vs target, option A vs option B, issue vs action, plan vs actual, scope vs deliverables.roadmap: phased plan. Useleft_content,content, andright_contentfor three phases.matrix: prioritization or portfolio logic. Use short labels and a bullet explanation.kpi: KPI dashboard or value scorecard. Use 3-5 metrics in bullets if structured metric fields are unavailable.risk: risk and mitigation page.next_steps: execution actions with owners, timing, and decision needs.
Formatting constraints:
- Do not put more than 6 bullets on one page.
- Keep bullets concise: one idea per bullet, preferably under 22 words.
- Avoid paragraphs inside slide content. Split paragraphs into bullets.
- Add a chapter divider every 4-6 business pages for decks longer than 10 slides.
- Prefer 2-column layouts when a page naturally contains contrast, trade-offs, or ownership split.
- Keep one language per deck. For Chinese requests, use Chinese slide titles, bullets, section names, chart labels, and action labels; avoid English defaults unless the user asks for bilingual material.
- Clean Markdown before calling the PPT tool. Do not send raw
#headings,**bold**, Markdown tables, block quotes, or long prose into slide fields. - Use varied page families deliberately:
roadmapfor phased plans,matrixfor prioritization,kpifor scorecards,riskfor risk registers, andnext_stepsfor action plans. - Do not leave placeholder bullets like "TBD" or "more analysis needed"; write the exact assumption or evidence gap.
Deck Presets
strategy
Use for strategy recommendations, transformation plans, market entry, growth, operating model, and roadmap decks.
Recommended structure:
- Executive Answer
- Strategic Context
- Current State vs Target State
- Strategic Options
- Recommended Path
- Initiative Portfolio
- Roadmap and Investment Logic
- Governance, KPI and Next Steps
Suggested format:
- Use
titlefor "Strategic Direction" and "Roadmap and Governance" dividers. - Use
two_columnfor current vs target and option trade-offs. - Use
roadmapfor implementation path. - Use
kpifor success metrics. - Use
next_stepsfor management actions.
proposal
Use for client proposals and commercial materials.
Recommended structure:
- Client Situation and Need
- Our Understanding of the Challenge
- Proposed Approach
- Scope and Deliverables
- Team, Timeline and Ways of Working
- Commercials, Risks and Next Steps
Suggested format:
- Use
titlefor "Client Need", "Proposed Solution", and "Mobilization". - Use
two_columnfor scope vs deliverables and client role vs consulting team role. - Use
roadmapfor timeline. - Use
riskfor delivery risks and mitigations.
project-update
Use for project status, steering committee updates, and delivery governance.
Recommended structure:
- Executive Status
- Progress vs Plan
- Workstream Highlights
- Risks, Issues and Decisions
- Value and Adoption Signals
- Next Steps
Suggested format:
- Use
two_columnfor progress vs plan. - Use
riskfor risks, issues, and decisions. - Use
kpifor value and adoption signals. - Use
next_stepsfor the next action cycle.
Quality Standard
- Default to 10-16 slides unless the user asks otherwise.
- Every slide needs an action-oriented title and 3-6 substantive bullets.
- Each content slide should contain at least one of: evidence, implication, decision, risk, owner, KPI, or next action.
- Every management-facing slide should be able to stand alone: a partner should understand the recommendation, basis, owner, and decision need without reading speaker notes.
- Prefer concrete numbers and ranges when exact data is missing: timeline, impact range, investment envelope, adoption target, KPI baseline, risk threshold, or