Triggered when user wants to create a presentation, slide deck, slides, or interactive HTML slide deck. Matches: "create a presentation", "make a slide deck", "build slides", "presentation for [audience]", "pitch deck", "status update slides", "training presentation", "proposal slides", "help me with a deck", "keynote slides", "PowerPoint presentation", "PPTX", "investor deck", "sales deck", "quarterly update", "interactive HTML slide deck". Also trigger when user explicitly asks for slides or a deck, even without the word "presentation". Do NOT use for written reports, memos, or documents in prose form (use report-writer), meeting notes or call summaries (use meeting-notes), budget creation (use budget-wizard — though presentation can chain to budget-wizard for cost slides), data visualization tools or dashboards (not a slide deck), or "show me" requests that mean list or table output rather than a slide presentation.
From tandemnpx claudepluginhub binatrixai/tandem-marketplace --plugin tandemThis skill is limited to using the following tools:
evals/evals.jsonexamples/pitch-deck.mdexamples/status-update.mdreferences/examples/pitch-deck.mdreferences/examples/status-update.mdreferences/template.mdtemplate.mdDispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Create structured slide decks through guided conversation. Output is markdown with slide structure, key points, and speaker notes.
Detect the user's preferred language from Personal Preferences. Respond entirely in that language.
If no preference is set:
AskUserQuestion: "What language should this presentation be in?"
Options: ["English", "עברית", "Русский"]
AskUserQuestion: "What type of presentation are you creating?"
Options: ["Pitch / Sales deck", "Status update / Report", "Training / Educational", "Proposal / Recommendation", "Custom"]
AskUserQuestion: "Who is the audience?"
Options: ["Executives / Leadership", "Team / Colleagues", "Clients / Customers", "Investors", "General / Mixed audience", "Custom — I'll describe"]
AskUserQuestion: "How many slides?"
Options: ["5 slides (quick overview)", "10 slides (standard)", "15 slides (detailed)", "Custom number"]
AskUserQuestion: "What format do you want?"
Options: ["Markdown outline (with speaker notes)", "Interactive HTML slide deck (open in browser)", "Both"]
If HTML or Both selected: Apply the HTML Slide Deck rules below when generating slides in Step 6.
Gather the core content through conversation:
AskUserQuestion: "How would you like to provide the content?"
Options: [
"I'll describe the topic — you create the outline",
"I have bullet points — organize them into slides",
"I have a document — extract key points into slides",
"Use a standard outline for [type] and I'll fill in details"
]
If using a standard outline, present the recommended structure for the selected type (see Type-Specific Structures below).
Present the proposed slide outline (titles only) for approval:
AskUserQuestion: "Here's the proposed outline. What would you like to do?"
Options: ["Looks good — generate full slides", "Reorder slides", "Add a slide", "Remove a slide", "Change a title"]
For each slide, produce:
Use the format from template.md.
AskUserQuestion: "Presentation is ready. What would you like to do?"
Options: ["Looks great — save it", "Edit a specific slide", "Change the tone", "Add more detail", "Make it shorter", "Switch to HTML format", "Switch to markdown format"]
If "Edit a specific slide": Ask which slide number, then what to change
If "Change the tone": Ask for target tone (more formal, more casual, more persuasive)
If "Save it": Save to ~/Tandem/documents/presentation-[topic]-[date].md
For each slide, include one visual recommendation:
| Content Type | Suggested Visual |
|---|---|
| Comparison | Side-by-side columns or table |
| Progress | Timeline or Gantt-style bar |
| Metrics | Bar chart, line graph, or big number |
| Process | Flowchart or numbered steps |
| Team | Photo grid with name/role |
| Market data | Pie chart or stacked bar |
| Quote/Testimonial | Large quote with attribution |
| Problem/Solution | Before/After split |
When HTML output is selected, generate a single self-contained HTML file with fullscreen slides, keyboard navigation, and polished visual components.
| Token | Value |
|---|---|
| Background | #0a0a0a |
| Text primary | #ffffff |
| Text secondary | #a0a0a0 |
| Card surface | #1a1a1a |
| Card border | #2a2a2a |
| Font | System sans-serif (no CDN required) |
| Heading size | 48-64px bold |
| Body size | 24-28px |
| Stat number size | 72-96px in accent color |
Pick one accent color per deck based on topic:
| Topic Area | Color | Hex |
|---|---|---|
| AI / Tech | Electric blue | #3B82F6 |
| Business / Finance | Warm amber | #F59E0B |
| Design / Creative | Coral pink | #F43F5E |
| Health / Wellness | Soft teal | #14B8A6 |
| Education | Royal purple | #8B5CF6 |
| Marketing / Sales | Vibrant orange | #F97316 |
| General | Clean white | #E5E5E5 |
If user has brand colors in memory, use those instead.
Every slide MUST have a visual component. Text-only slides are NOT allowed. Choose from:
| Component | Use For | Structure |
|---|---|---|
| Card Grid | Features, benefits, categories | 2-4 cards with icon/emoji, title, one-line description |
| Comparison Panel | Old vs new, A vs B | Two columns with a "vs" divider |
| Stat Callout | Key numbers, growth, costs | One huge number (72-96px) in accent color with label |
| Step Flow | Processes, tutorials | Horizontal or vertical numbered steps with arrows |
| Quote Block | Testimonials, key statements | Large quotation marks, italic text, attribution |
| Icon + Label List | Feature lists, agendas | Vertical list with emoji/icons on left, labels on right |
| Code Block | Code examples, configs | Monospace on dark card with syntax coloring |
| Timeline | Roadmaps, history | Horizontal line with dots and labels |
| Metric Dashboard | KPIs, performance data | 3-4 stat boxes in a row with label and value |
| Comparison Grid | Multi-item comparison | Rows and columns with checkmarks or values |
Save as presentation-[topic]-[date].html alongside the markdown file (if both formats selected).
The file must be completely self-contained — opening in any browser displays the full interactive deck.
After completion, suggest 1-2:
Memory is user-triggered only. Offer to remember:
Follow template.md for slide format. See examples/pitch-deck.md and examples/status-update.md for complete examples.
For HTML slide decks, generate self-contained HTML following the HTML Slide Deck Mode section above.
When creating Hebrew presentations:
After completing the workflow, append an entry to ~/Tandem/stats.json:
{
"type": "document",
"action": "created",
"count": 1,
"timeSavedMinutes": 30,
"description": "Created presentation: Investor Pitch Deck (12 slides)",
"timestamp": "<current ISO 8601>"
}
If ~/Tandem/stats.json does not exist, create it as [<entry>]. If it exists, read it, parse the JSON array, append the new entry, and write it back.
After appending to stats.json, follow the /sync workflow from tandem-skills/core/sync/SKILL.md to rebuild ~/Tandem/dashboard.html with updated statistics. This keeps the dashboard current after every skill run. If /sync fails (e.g., dashboard.html does not exist yet), continue — the main skill workflow must complete successfully regardless of sync outcome.