Fetches revealjs from ryanbbrown/revealjs-skill and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/revealjs
Restart Cursor to activate revealjs. Access via /revealjs in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
✅ Be consistent: repeat patterns, spacing, and visual language across slides
✅ Always use pt (points) for font sizes - slides are fixed-size, so pt is predictable and familiar (like PowerPoint/Keynote). Never use em, rem, or px for font sizes.
Color Palette Selection
Choosing colors creatively:
Think beyond defaults: What colors genuinely match this specific topic? Avoid autopilot choices.
The scaffold script automatically copies base-styles.css to your presentation directory as styles.css. Now customize the CSS variables (especially colors) for your presentation theme.
Using Google Fonts: Add an @import at the top of your CSS file:
:root{/* ===========================================
BACKGROUND COLOR - Set this first!
=========================================== */--background-color:#ffffff;/* Change for dark themes (e.g., #1a1a2e) *//* Typography - ALWAYS use pt for font sizes */--heading-font:"Source Sans Pro", Helvetica, sans-serif;--body-font:"Source Sans Pro", Helvetica, sans-serif;--base-font-size:32px;/* Only px value - sets reveal.js base */--text-size:16pt;/* Base body text - intentionally small */--h1-size:48pt;--h2-size:36pt;--h3-size:24pt;/* Colors - customize these for each presentation */--primary-color:#2196F3;--secondary-color:#ff9800;--text-color:#222;/* Use light color (e.g., #FAF7F2) for dark backgrounds */--muted-color:#666;/* Adjust for dark backgrounds too */}
Text size utilities (use these to scale up text when slides have less content):
/* Base text is 16pt - use these classes to increase size when needed */.text-lg{font-size:18pt;}/* Slightly larger */.text-xl{font-size:20pt;}/* Medium emphasis */.text-2xl{font-size:24pt;}/* Strong emphasis */.text-3xl{font-size:28pt;}/* Very large */.text-4xl{font-size:32pt;}/* Maximum body text */.text-muted{color:var(--muted-color);}.text-center{text-align: center;}
Typography guidance:
Base text (--text-size: 16pt) is intentionally small to fit more content
When a slide has less content, use .text-lg, .text-xl, etc. to fill space appropriately
This approach prevents overflow on content-heavy slides while allowing flexibility on lighter slides
Custom CSS classes for repeated patterns:
Use inline styles for layout (grids, flex containers) since those vary per slide. But when a visual pattern appears on multiple slides, create a dedicated CSS class in styles.css instead of repeating inline styles. This keeps the HTML clean and ensures consistency. Common examples: stat boxes (number + label), feature cards (icon + title + description), timeline/process steps, profile/bio cards. If an element repeats 3+ times, it should be a class.
Step 4: Fill in the HTML Content
IMPORTANT: Use the Edit tool to fill in slides incrementally — one or a few slides at a time. Do NOT rewrite the entire HTML file with the Write tool. The scaffold generates unique placeholder text per slide (e.g., Slide 2 Title Here), so each section can be targeted with Edit. This is more token-efficient and less error-prone than generating the full file at once.
Follow these patterns:
Standard slide structure:
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
