Skills now ship with the app under /apps/skills/ (sibling of /apps/x).
Forge bundles the directory into Resources/skills/; main resolves it via
process.resourcesPath in production and a workspace-relative path in dev,
then registers it in the DI container. The runtime reads SKILL.md files
directly from the bundle — no copy to ~/.rowboat/skills/, no GitHub
tarball sync.
Drop the override layer (FSSkillsRepo, SkillOverride, edit/diff UI,
skill-update notification) since skills are now read-only and only ship
with app updates. Resolver simplifies to a single source.
Add a placeholder substitution layer so skills that need live data
(currently `tracks`, with {{TRACK_BLOCK_SCHEMA}}) keep dynamic content
without depending on TS-module evaluation.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
115 KiB
| name | description | license | compatibility | metadata | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| create-presentations | Create PDF presentations and slide decks from natural language requests using knowledge base context. Use when the user wants to create a presentation, pitch deck, or slide deck. | MIT | Designed for Rowboat desktop app |
|
PDF Presentation Skill
Theme Selection
If the user specifies a visual theme, colors, or brand guidelines, use those. If they do NOT specify a theme, do not ask — pick the best fit based on the topic and audience:
- Dark Professional — Deep navy/charcoal backgrounds, indigo (#6366f1) and violet (#8b5cf6) accents, white text. Best for: tech, SaaS, keynotes, engineering.
- Light Editorial — White/warm cream backgrounds, amber (#f59e0b) and stone accents, dark text with serif headings. Best for: reports, proposals, thought leadership, research.
- Bold Vibrant — Mixed dark and light slides, emerald (#10b981) and rose (#f43e5c) accents, high contrast. Best for: pitch decks, marketing, creative, fundraising.
Note the theme used at the end of delivery so the user can request a swap if they prefer a different look.
Visual Consistency Rules
Every presentation must have a unified color theme applied across ALL slides. Do not mix unrelated color palettes between slides.
- Define a theme palette upfront — Pick one primary color, one accent color, and one neutral base (dark or light). Use these consistently across every slide.
- Backgrounds — Use at most 2-3 background variations (e.g. dark base, light base, and primary color). Alternate them for rhythm but keep them from the same palette.
- Accent color — Use the same accent color for all highlights: overlines, bullets, icons, chart fills, timeline dots, CTA buttons, divider lines.
- Typography colors — Headings, body text, and muted text should use the same tones on every slide. Don't switch between warm and cool grays mid-deck.
- Charts and data — Use shades/tints of the primary and accent colors for chart fills. Never introduce one-off colors that don't appear elsewhere in the deck.
- Consistent fonts — Pick one heading font and one body font. Use them on every slide. Don't mix different heading fonts across slides.
Critical: One Theme Per Deck
The example layouts in this document each use different colors and styles for showcase purposes only. When building an actual presentation, pick ONE theme and apply it consistently to EVERY slide. Borrow layout structures and patterns from the examples, but replace all colors, fonts, and backgrounds with your chosen theme's palette. Never copy the example colors verbatim — adapt them to the unified theme.
Visual Consistency Rules
Every presentation must have a unified color theme applied across ALL slides. This is the #1 most important design rule. A deck where every slide looks like it belongs together is always better than a deck with individually beautiful but visually inconsistent slides.
Background Strategy (STRICT)
Pick ONE dominant background tone and use it for 80%+ of slides. Add subtle variation within that tone — never alternate between dark and light backgrounds.
For dark themes:
Deep base (e.g. #0f172a) — use for title, section dividers, closing (primary background) Medium base (e.g. #1e293b or #111827) — use for content slides, charts, tables (secondary background) Accent pop (e.g. #6366f1) — use for 1-2 key stat or quote slides only (rare emphasis) NEVER use white or light backgrounds in a dark-themed deck. Data tables, team grids, and other content that "feels light" should still use the dark palette with adjusted contrast.
For light themes:
Light base (e.g. #fafaf9 or #ffffff) — use for most content slides (primary background) Warm tint (e.g. #fefce8 or #f8fafc) — use for alternation and visual rhythm (secondary background) Accent pop (e.g. the theme's primary color) — use for 1-2 key stat or quote slides only (rare emphasis) NEVER use dark/navy backgrounds in a light-themed deck.
Never alternate between dark and light backgrounds. This creates a jarring strobe effect and breaks visual cohesion. The audience's eyes have to constantly readjust. Instead, create rhythm through subtle shade variation within the same tone family. Never use more than 3 background color values across the entire deck.
Color & Typography Rules
Define a theme palette upfront — Pick one primary color, one accent color, and one neutral base (dark or light). Use these consistently across every slide. Write these as CSS variables and reference them everywhere. Accent color — Use the SAME accent color for ALL highlights across the entire deck: overlines, bullets, icons, chart fills, timeline dots, CTA buttons, divider lines. Do not use different accent colors on different slides. Typography colors — Headings, body text, and muted text should use the same tones on every slide. Don't switch between warm and cool grays mid-deck. Charts and data — Use shades/tints of the primary and accent colors for chart fills. Never introduce one-off colors that don't appear elsewhere in the deck. Consistent fonts — Pick one heading font and one body font. Use them on every slide. Don't mix different heading fonts across slides.
Title Slide Rules
Title text must span the FULL slide width. Never place a decorative element beside the title that competes for horizontal space. Title slides should use a single-column, vertically-stacked layout: overline → title → subtitle → optional tags/pills. No side-by-side elements on title slides. If a decorative visual is needed, place it BEHIND the text (as a CSS background, gradient, or pseudo-element), never beside it. Title font-size must not exceed 64px. For titles longer than 5 words, use 48px max.
Content Planning (Do This Before Building)
Before writing any HTML, plan the narrative arc:
- Hook — What's the opening statement or question that grabs attention?
- Core argument — What's the one thing the audience should remember?
- Supporting evidence — What data, examples, or frameworks back it up?
- Call to action — What should the audience do next?
Map each point to a slide layout from the Available Layout Types below. For a typical presentation, generate 8-15 slides: title + agenda (optional) + 6-10 content slides + closing. Don't pad with filler — every slide should earn its place. Use layout variety — never use the same layout for consecutive slides.
Workflow
- Use workspace-readFile to check knowledge/ for relevant context about the company, product, team, etc.
- Ensure Playwright is installed: `npm install playwright && npx playwright install chromium`
- Use workspace-getRoot to get the workspace root path.
- Plan the narrative arc and slide outline (see Content Planning above).
- Use workspace-writeFile to create the HTML file at tmp/presentation.html (workspace-relative) with slides (1280x720px each).
- Perform the Post-Generation Validation (see below). Fix any issues before proceeding.
- Use workspace-writeFile to create the conversion script at tmp/convert.js (workspace-relative) — see Playwright Export section.
- Run it: `node <WORKSPACE_ROOT>/tmp/convert.js`
- Tell the user: "Your presentation is ready at ~/Desktop/presentation.pdf" and note the theme used.
Critical: Never show HTML code to the user. Never ask the user to run commands, install packages, or make technical decisions. The entire pipeline from content to PDF must be invisible to the user.
Use workspace-writeFile and workspace-readFile for ALL file operations. Do NOT use executeCommand to write or read files.
Post-Generation Validation (REQUIRED)
After generating the slide HTML, perform ALL of these checks before converting to PDF:
-
Title overflow check: For every slide, verify that the title text at its set font-size fits within the slide width (1280px) minus padding (120px total). If `title_chars × 0.6 × font_size > 1160`, reduce font-size. Use these max sizes:
- Short titles (1-3 words): 72px max
- Medium titles (4-6 words): 56px max
- Long titles (7+ words): 44px max Apply `word-wrap: break-word` and `overflow-wrap: break-word` to all title elements. Never use `white-space: nowrap` on titles.
-
Content bounds check: Verify no element extends beyond the 1280x720 slide boundary. Look for: long titles, bullet lists with 6+ items, wide tables, long labels on charts, text that wraps more lines than the available height allows.
-
Broken visuals check: Confirm no `` tags reference external URLs. All visuals must be CSS, SVG, or emoji only. Never use external images — they will fail in PDF rendering. Use CSS shapes, gradients, SVG, or emoji for all visual elements.
-
Font loading check: Verify the Google Fonts `` tag includes ALL font families used in the CSS. Missing fonts cause fallback rendering and broken typography.
-
Theme consistency check: Confirm all slides use the same palette — no rogue colors in charts, backgrounds, or text that don't belong to the chosen theme.
-
Fix before proceeding: If any check fails, fix the HTML before PDF conversion. Do not proceed with known issues.
PDF Export Rules
These rules prevent rendering issues in PDF. Violating them causes overlapping rectangles and broken layouts.
- No layered elements — Never create separate elements for backgrounds or shadows. Style content elements directly.
- No box-shadow — Use borders instead: `border: 1px solid #e5e7eb`
- Bullets via CSS only — Use `li::before` pseudo-elements, not separate DOM elements.
- Content must fit — Slides are 1280x720px with 60px padding. Safe content area is 1160x600px. Use `overflow: hidden`.
- No footers or headers — Never add fixed/absolute-positioned footer or header elements to slides. They overlap with content in PDF rendering. If you need a slide number or title, include it as part of the normal content flow.
- No external images — All visuals must be CSS, SVG, or emoji. External image URLs will render as broken white boxes in PDF.
Required CSS
```css @page { size: 1280px 720px; margin: 0; } html { -webkit-print-color-adjust: exact !important; print-color-adjust: exact !important; } .slide { width: 1280px; height: 720px; padding: 60px; overflow: hidden; page-break-after: always; page-break-inside: avoid; } .slide:last-child { page-break-after: auto; } ```
Playwright Export
```javascript // save as tmp/convert.js via workspace-writeFile const { chromium } = require('playwright'); const path = require('path');
(async () => { const browser = await chromium.launch(); const page = await browser.newPage(); // Replace <WORKSPACE_ROOT> with the actual absolute path from workspace-getRoot await page.goto('file://<WORKSPACE_ROOT>/tmp/presentation.html', { waitUntil: 'networkidle' }); await page.pdf({ path: path.join(process.env.HOME, 'Desktop', 'presentation.pdf'), width: '1280px', height: '720px', printBackground: true, }); await browser.close(); console.log('Done: ~/Desktop/presentation.pdf'); })(); ```
Replace `<WORKSPACE_ROOT>` with the actual absolute path returned by workspace-getRoot.
Available Layout Types (35 Templates)
Use these as reference when building presentations. Pick the appropriate layout for each slide based on the content type. Mix and match for visual variety.
Title & Structure Slides
- Title Slide (Dark Gradient) — Hero opening with gradient text and atmospheric glow
- Title Slide (Light Editorial) — Clean, warm serif typography with editorial feel
- Section Divider — Chapter break with oversized background number
- Agenda / Table of Contents — Serif title with numbered items and descriptions
- Full-Bleed Cinematic — Atmospheric background with grid texture, orbs, and bottom-aligned content
Content Slides
- Big Statement / Quote — Full-color background with bold quote or key takeaway
- Big Stat Number — Single dramatic metric with context text
- Bullet List (Split Panel) — Dark sidebar title + light content area with icon bullets
- Numbered List — Ordered steps in numbered cards
- Two Columns — Side-by-side content cards
- Three Columns with Icons — Feature cards with icon accents
- Image + Text — Visual panel left, content + CTA right
- Image Gallery (2x2) — Grid of captioned visual cards using CSS gradient backgrounds
Chart & Data Slides
- Bar Chart (Vertical) — Vertical bars with gradient fills and labels
- Horizontal Bar Chart — Ranked bars for lists with long labels
- Stacked Bar Chart — Segmented bars showing composition/breakdown
- Combo Chart (Bar + Line) — SVG bars for volume + line for growth rate
- Donut Chart — CSS conic-gradient donut with legend
- Line Chart (SVG) — SVG polyline with area fill and data labels
- KPI Dashboard — Color-coded metric cards with change indicators
- Data Table — Styled rows with colored header and status badges
- Feature Matrix — Checkmark comparison table (features x tiers)
Diagram Slides
- Horizontal Timeline — Connected milestone dots on a horizontal axis
- Vertical Timeline — Left-rail progression of milestones
- Process Flow — Step cards connected with arrows
- Funnel Diagram — Tapered width bars showing conversion stages
- Pyramid Diagram — Tiered hierarchy showing levels/priorities
- Cycle Diagram — Flywheel/feedback loop with circular node arrangement
- Venn Diagram — Three translucent overlapping circles
- 2x2 Matrix — Four color-coded quadrants with axis labels
Comparison Slides
- Comparison / Vs — Split layout with contrasting colors for A vs B
- Pros & Cons — Checkmarks vs. warnings in two columns
- Pricing Table — Tiered cards with featured highlight
People & Closing Slides
- Team Grid — Avatar circles with role descriptions
- Thank You / CTA — Atmospheric closing with contact details
Layout Selection Heuristic
For each slide, identify the content type and pick the matching layout:
| Content Type | Best Layouts |
|---|---|
| Opening / hook | Title Slide, Full-Bleed Cinematic |
| Agenda / overview | Agenda/TOC |
| Key metric or stat | Big Stat Number, KPI Dashboard |
| List of points | Bullet List, Numbered List |
| Features or pillars | Three Columns, Two Columns |
| Trend over time | Line Chart, Horizontal Timeline |
| Composition / breakdown | Donut Chart, Stacked Bar, Pie |
| Ranking | Horizontal Bar Chart |
| Comparison | Vs Slide, Pros & Cons |
| Process or steps | Process Flow, Vertical Timeline |
| Hierarchy | Pyramid Diagram |
| Feedback loop | Cycle Diagram |
| Overlap / intersection | Venn Diagram |
| Prioritization | 2x2 Matrix |
| Data details | Data Table, Feature Matrix |
| Pricing | Pricing Table |
| Emotional / cinematic | Big Statement, Full-Bleed Cinematic |
| Team intro | Team Grid |
| Closing | Thank You / CTA |
Never use the same layout for consecutive slides. Alternate between dark and light backgrounds for rhythm.
Design Guidelines
- Use Google Fonts loaded via `` tag. Recommended pairings:
- Primary pair: Outfit (headings) + DM Sans (body) — works for most decks
- Editorial pair: Playfair Display (headings) + DM Sans (body) — for reports/proposals
- Accent fonts: Space Mono (overlines, labels), Crimson Pro (quotes)
- Dark slides: use subtle radial gradients for atmosphere, semi-transparent overlays for depth
- Light slides: use warm neutrals, clean borders, and ample whitespace
- Charts: use CSS (conic-gradient for donuts, inline styles for bar heights) or inline SVG for line/combo charts
- Typography hierarchy: monospace overlines for labels -> sans-serif for headings -> serif for editorial/quotes
- Cards: use `border-radius: 12-16px`, subtle borders (`rgba(255,255,255,0.08)` on dark), no box-shadow (PDF rule)
- All visuals must be CSS, SVG, or emoji — no external images
HTML Template Examples
<html lang="en"> <head> </head>The Future of AI Coworkers
35 production-ready slide templates across different layouts, chart types, diagrams, and visual styles — all themed around the AI-powered workplace.
The Future of
AI Coworkers
Working Alongside AI
The Rise of Intelligent Collaboration
AI coworkers don't replace human creativity — they amplify it, handling the routine so teams can focus on the extraordinary.
Key Benefits of AI Coworkers
10x Faster Research
AI agents synthesize thousands of documents in seconds, surfacing insights that would take humans weeks.
Proactive Task Management
Intelligent assistants anticipate next steps, draft follow-ups, and keep projects on track automatically.
Always-On Collaboration
AI coworkers bridge time zones, summarize meetings, and ensure no team member is ever out of the loop.
Continuous Learning
Each interaction makes the AI smarter — building a compounding knowledge base for your entire organization.
Two Modes of AI Collaboration
🧠 Thinking Partner
AI coworkers serve as brainstorming partners that challenge assumptions, offer alternative perspectives, and help teams explore ideas they wouldn't have considered alone. They bring pattern recognition across vast datasets to creative problem-solving sessions.
⚙️ Execution Engine
From drafting reports to analyzing data pipelines, AI coworkers handle the heavy lifting of execution. They turn rough outlines into polished deliverables, automate repetitive workflows, and free humans to focus on strategy and relationship building.
Core Capabilities
Deep Research
Analyze millions of data points across your organization's knowledge base to surface critical insights and connections.
Content Creation
Draft, edit, and refine documents, presentations, and communications tailored to your brand voice and standards.
Workflow Orchestration
Connect tools, automate handoffs, and ensure seamless execution across your entire tech stack and team.
Productivity Gains by Department
How Teams Use AI Coworkers
AI Coworker Adoption Rate
The Evolution of AI Coworkers
Launch AI Knowledge Graph
Persistent memory layer that maps relationships across all work data — emails, meetings, docs.
Multi-Agent Orchestration
Deploy specialized agents that collaborate — research agent, writing agent, code agent — working in concert.
Proactive Insights Engine
AI coworker surfaces insights before you ask — flagging risks, opportunities, and action items automatically.
Full Workflow Autonomy
End-to-end autonomous task completion with human-in-the-loop oversight for critical decisions.
How AI Coworkers Learn Your Workflow
Connect
Integrate with your tools — email, calendar, Slack, docs
Observe
AI maps your workflows, relationships, and patterns
Assist
Proactively suggests actions and drafts deliverables
Evolve
Gets smarter with every interaction, compounding value
Impact Metrics — Q4 2026
Traditional Workflow
- Manual research across scattered sources
- Hours spent formatting reports and decks
- Context lost between meetings and tools
- Repetitive tasks drain creative energy
- Knowledge silos across the org
With AI Coworkers
- Instant synthesis from all data sources
- Auto-generated first drafts in seconds
- Persistent memory across every interaction
- Automation frees focus for high-impact work
- Shared intelligence for the entire team
Choose Your AI Coworker Plan
- 1 AI coworker agent
- 5 tool integrations
- 10K messages / month
- 7-day memory window
- 5 AI coworker agents
- Unlimited integrations
- Unlimited messages
- Persistent memory
- Knowledge graph
- Unlimited agents
- Custom model training
- SSO & compliance
- Dedicated support
- On-premise option
Meet Your AI Team
Research Agent
Writing Agent
Code Agent
Data Agent
Your AI Coworker Remembers Everything
Unlike session-based tools that forget after every chat, AI coworkers build persistent knowledge graphs from your emails, meetings, and documents — compounding intelligence over time.
See It In Action →AI Coworker Adoption Funnel
Thank You
AI Task Distribution by Department
Top AI Coworker Use Cases
AI Coworker Platform Comparison
| Platform | Response Time | Memory | Integrations | Status |
|---|---|---|---|---|
| AiCo Pro | 0.8s avg | Persistent | 140+ | Leader |
| WorkBot AI | 1.2s avg | Session only | 85+ | Growing |
| TeamMind | 1.5s avg | 7-day window | 60+ | Growing |
| AssistIQ | 2.1s avg | Session only | 35+ | Emerging |
| CoPilotX | 0.9s avg | 30-day window | 110+ | Leader |
AI Coworker Revenue & Growth
AI Coworker Maturity Model
The AI Coworker Flywheel
Ingest
Connects to emails, docs, meetings, and tools
Learn
Maps patterns, preferences, and relationships
Act
Automates tasks and generates deliverables
Improve
Feedback refines accuracy and relevance
Intelligence
The AI Coworker Sweet Spot
Awareness
Action
Learning
Coworker
AI Coworker Task Prioritization Matrix
🚀 Automate Now
High frequency, low complexity tasks like scheduling, data entry, meeting notes, and status updates.
🤝 Augment & Assist
High frequency, high complexity tasks like code review, research synthesis, and report drafting.
📋 Batch & Template
Low frequency, low complexity tasks like onboarding docs, expense reports, and form filling.
🧠 Strategic Co-Pilot
Low frequency, high complexity tasks like strategy planning, crisis response, and deal negotiation.
AI Coworkers in Action
Intelligent Chat
Context-aware conversations with persistent memory
Auto-Generated Reports
Data pulled and visualized in seconds
Seamless Integrations
140+ tools connected out of the box
Enterprise Security
SOC 2 compliant with full audit trails
5 Rules for AI Coworker Success
Start with High-Volume Tasks
Deploy AI where repetition is highest — email, scheduling, summaries.
Give Context Generously
The more your AI knows about your work, the better it performs.
Trust But Verify
Review AI outputs initially, then gradually increase autonomy.
Build Feedback Loops
Correct mistakes — each correction makes the AI permanently smarter.
Expand Gradually
Once one workflow succeeds, replicate the pattern across the team.
AI Coworkers: Benefits & Considerations
- Instant access to organizational knowledge
- 24/7 availability across time zones
- Consistent quality on repetitive tasks
- Scales without proportional cost increase
- Learns and improves over time
- Requires initial setup and training period
- Data privacy policies must be established
- Change management for team adoption
- Best for structured, repeatable workflows
- Human oversight still needed for critical decisions
Feature Availability by Plan
| Feature | Starter | Team | Enterprise |
|---|---|---|---|
| Chat-based assistant | ✓ | ✓ | ✓ |
| Persistent memory | — | ✓ | ✓ |
| Knowledge graph | — | ✓ | ✓ |
| Multi-agent orchestration | — | — | ✓ |
| Custom model training | — | — | ✓ |
| SSO & compliance | — | — | ✓ |
| API access | — | ✓ | ✓ |
Today's Agenda
The Rise of AI Coworkers
Market landscape and driving forces
Core Capabilities
What makes an AI coworker different from a chatbot
Impact & Metrics
Real-world results from early adopters
Implementation Roadmap
How to get started in 90 days
Q&A and Next Steps
Open discussion and action items
Every Knowledge Worker Deserves an AI Teammate
We're building toward a world where AI handles the busywork and humans do what they do best — think creatively, build relationships, and make decisions that matter.