Menu
PptxGenJS pipeline for generating native .pptx presentations with brand tokens, 5 deck templates, and visual QA
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | pptx |
| description | PptxGenJS pipeline for generating native .pptx presentations with brand tokens, 5 deck templates, and visual QA |
| tier | 1 (universal) |
| auto-fire | /deck (pptx path) |
| user-invocable | false |
Defines the PptxGenJS pipeline for generating native .pptx presentations. Contains brand token integration specs, the 5 deck templates with 8 slides each, and the visual QA pipeline. This is the primary presentation generation path; Gamma is the alternative.
SalesSidekick generates presentations using PptxGenJS, a JavaScript library for creating PowerPoint files programmatically.
Generation flow:
Captured during /setup Phase 5 (Presentation Brand):
| Token | Description | Default |
|---|---|---|
| Logo | Company logo file (PNG/SVG) | SalesSidekick placeholder |
| Primary Color | Main brand color (hex) | #2563EB (blue) |
| Secondary Color | Accent color (hex) | #1E40AF (dark blue) |
| Background Color | Slide background (hex) | #FFFFFF (white) |
| Text Color | Primary text color (hex) | #1F2937 (dark gray) |
| Heading Font | Font for titles | Arial Bold |
| Body Font | Font for body text | Arial |
Each template produces exactly 8 slides. Templates auto-select based on deal stage but can be overridden by the user.
Auto-selects: Stage = Prospecting or Discovery
| Slide | Title | Content |
|---|---|---|
| 1 | Title Slide | {{COMPANY}} + prospect company name + meeting date |
| 2 | About Us | {{COMPANY}} overview — who we are, what we do (from company-intel) |
| 3 | Your World | Industry context — trends and challenges relevant to the prospect |
| 4 | Common Challenges | 3 pain points typical for their industry/size (from research or ICP) |
| 5 | How We Help | Approach overview — methodology, not features (Commandment 9) |
| 6 | Proof Points | 2-3 relevant case studies or metrics (evidence-graded) |
| 7 | Discovery Questions | Key questions to explore together (from MEDDPICC gaps) |
| 8 | Next Steps | Proposed agenda for follow-up, contact info |
Auto-selects: Stage = Qualification
| Slide | Title | Content |
|---|---|---|
| 1 | Title Slide | "Point of View: [Prospect Company]" + date |
| 2 | Executive Anchor | 2-sentence framing of their business challenge |
| 3 | The Blind Spot | Insight they haven't fully quantified (from POV model) |
| 4 | Math of Pain | Quantified cost of inaction (evidence-graded) |
| 5 | The Approach | How we solve it — methodology, not product (Commandment 9) |
| 6 | Proof: Similar Company | Case study from a similar company (industry, size) |
| 7 | Proof: Results | Specific metrics and outcomes (evidence-graded) |
| 8 | Recommended Next Step | Proportional CTA based on stage |
Auto-selects: Stage = Proposal
| Slide | Title | Content |
|---|---|---|
| 1 | Title Slide | "Executive Summary: [Prospect Company]" + date |
| 2 | Business Context | Their situation — what they told us (Verified from calls) |
| 3 | Agreed Requirements | Decision criteria confirmed in discovery (Verified) |
| 4 | Proposed Solution | What we're proposing — mapped to their requirements |
| 5 | Business Impact | ROI / projected outcomes (evidence-graded, show the math) |
| 6 | Implementation | Timeline, milestones, resource requirements |
| 7 | Investment | Pricing overview — positioned as investment, not cost |
| 8 | Decision & Next Steps | Proposed decision timeline, mutual action plan |
Auto-selects: Stage = Closed Won (existing customer)
| Slide | Title | Content |
|---|---|---|
| 1 | Title Slide | "Quarterly Business Review: [Customer]" + quarter |
| 2 | Relationship Summary | Account overview, key stakeholders, engagement history |
| 3 | Outcomes Achieved | What we've delivered — metrics and wins (Verified) |
| 4 | Usage & Adoption | How they're using the product — engagement data |
| 5 | Value Delivered | ROI realized vs. projected (evidence-graded) |
| 6 | Roadmap & Innovation | What's coming — relevant product updates |
| 7 | Growth Opportunities | Expansion possibilities — whitespace analysis |
| 8 | Next Quarter Plan | Agreed priorities and success metrics |
Auto-selects: Primary Competitor field is populated
| Slide | Title | Content |
|---|---|---|
| 1 | Title Slide | "Why [Our Company] vs [Competitor]" + date |
| 2 | Your Requirements | Decision criteria mapped (from discovery) |
| 3 | Approach Comparison | Methodology differences — not feature checklist |
| 4 | Where We Excel | 3 key differentiators with evidence (from battlecard) |
| 5 | Customer Evidence | Case study of customer who switched from competitor |
| 6 | Total Value | TCO or total value comparison (evidence-graded) |
| 7 | Risk of Status Quo | What they lose by staying with current approach |
| 8 | Transition Plan | How switching works — minimize risk, maximize speed |
When LibreOffice is available on the system:
libreoffice --headless --convert-to pdfWhen LibreOffice is NOT available:
Fires on any operation that reads or writes deal, company, contact, call note, or task data. Provides: file schemas, write protocol (entity + index + cross-references + ops.log), account name resolution (fuzzy matching), read-time validation, duplicate detection rules. Output contract: every data write follows the standard protocol and produces a FILES UPDATED block.
Fires when a user asks about deal strategy, how to approach a stalled deal, or needs a business case. Produces: Five-Lens Prism analysis (stakeholder psychology, political capital, competitive dynamics, hidden leverage, temporal dynamics), Three Paths recommendation (velocity/diagnostic/protective), 5-Component POV model. Output contract: three distinct strategic options with evidence grading, never a single recommendation.
Fires on meeting prep, outreach, research, deck creation, and business case building. Provides: company overview, product portfolio, market position, differentiators, pricing context, case studies by vertical, key selling metrics, voice & language patterns, pain signal mapping, and prism insights. Output contract: company-specific context that makes outputs relevant to the prospect's actual situation. When a Platform Document exists (from /research), loads enriched voice, pain, and strategic intelligence.
Fires when a competitor is mentioned, a competitive situation arises, or the user asks how to beat/displace/win against a specific vendor. Produces: per-competitor displacement playbook with strengths, weaknesses, talk tracks, proof points, trap questions, and landmine responses. Triggers on: handle-competition, think-about-deal (competitive lens), battle analysis.
Fires on any written output — emails, outreach, LinkedIn posts, business cases, follow-ups. Provides: voice rules, email formatting, vocabulary substitutions, banned phrases, sign-off, and 7-point voice check. Output contract: all written content matches the user's calibrated tone and style.
Fires when a call transcript is pasted or the user says they finished a call. Produces: 6 structured outputs — MEDDPICC scoring with evidence, task extraction with owners and dates, coaching feedback on 5 dimensions, follow-up email in 3 tones, risk signals with mitigation actions, competitive intel. Output contract: every output is actionable, not just analytical.