Generate professional PowerPoint pitch decks following industry best practices. This skill creates structured presentations for fundraising, sales, and business development using a proven 10-slide format.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpitch-deckExecute the skills CLI command in your project's root directory to begin installation:
Fetches pitch-deck from ailabs-393/ai-labs-claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate pitch-deck. Access via /pitch-deck in your agent's command palette.
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.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
344
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
344
stars
Generate professional PowerPoint pitch decks following industry best practices. This skill creates structured presentations for fundraising, sales, and business development using a proven 10-slide format.
Activate this skill when users request:
Collect necessary information from the user to populate the pitch deck. Use a conversational approach to gather details across the following categories:
Required information:
Recommended information (include if available): 5. Market opportunity: Market size (TAM/SAM/SOM), growth rate, market trends 6. Product details: Product features, screenshots, technology highlights 7. Traction: Key metrics, revenue, users, growth rate, milestones, customer testimonials 8. Competition: Competitors, competitive advantages, differentiation 9. Team: Founders and key team members with relevant background 10. Financials & Ask: Funding amount, use of funds, financial projections, milestones
Approach:
Organize the gathered information into the standard pitch deck structure:
Reference best practices: For detailed guidance on each slide's content and structure, consult references/pitch_deck_best_practices.md. Search for specific sections using grep:
grep -A 10 "### [Slide Number]. [Slide Name]" references/pitch_deck_best_practices.md
Format the collected information as a JSON file that will be consumed by the pitch deck generation script. Create a file called pitch_data.json with the following structure:
{
"company_name": "Company Name",
"tagline": "One-line description of what you do",
"problem": [
"Problem statement 1 with data/statistics",
"Problem statement 2 showing impact",
"Problem statement 3 demonstrating urgency"
],
"solution": [
"How your product solves the problem",
"Key feature 1 and its benefit",
"Key feature 2 and its benefit",
"Unique value proposition"
],
"market": [
"TAM: Total addressable market with $ figure",
"SAM: Serviceable available market",
"SOM: Serviceable obtainable market",
"Market growth rate and trends"
],
"product": [
"Product feature 1",
"Product feature 2",
"Technology highlights",
"User experience benefits"
],
"traction": [
"Revenue: $X (YY% growth)",
"Users: X,XXX active users",
"Key milestone 1",
"Customer testimonial or social proof"
],
"business_model": [
"Revenue model (e.g., SaaS subscription)",
"Pricing: $XX/month per user",
"Unit economics: CAC, LTV, margins",
"Sales channels"
],
"competition": {
"our_advantages": [
"Advantage 1",
"Advantage 2",
"Unfair advantage/defensibility"
],
"competitors": [
"Competitor 1",
"Competitor 2",
"Alternative solutions"
]
},
"team": [
"Founder 1: Name - Background and relevant experience",
"Founder 2: Name - Background and relevant experience",
"Key hire: Name - Background and why they matter",
"Notable advisors"
],
"financials": [
"Raising: $X seed/Series A round",
"Use of funds: XX% engineering, XX% sales, XX% ops",
"Milestones with this funding",
"Runway: X-X months to next milestone"
]
}
Notes:
company_nameour_advantages and competitors keys (for two-column layout) or a simple arrayExecute the Python script to create the PowerPoint presentation:
python3 scripts/create_pitch_deck.py pitch_data.json output_filename.pptx
The script will:
.pptx file ready for presentation or further customizationPresent the generated pitch deck location to the user and offer to:
Iteration approach:
The generated pitch deck follows these design principles:
Color Scheme:
Typography:
Layout:
Visual Hierarchy:
For detailed guidance on pitch deck content, structure, and presentation tips, reference:
references/pitch_deck_best_practices.md - Comprehensive guide covering:
Load this reference when providing detailed advice on pitch content or structure.
Scenario 1: Early-stage startup seeking seed funding
Scenario 2: Growth-stage company creating sales deck
Scenario 3: Product launch presentation
After generating the base deck:
Script errors:
python-pptx library is installed: pip3 install python-pptxContent issues:
create_pitch_deck.py: Python script that generates PowerPoint presentations from structured JSON datapitch_deck_best_practices.md: Comprehensive guide on pitch deck content, structure, and design principlesMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
pproenca/dot-skills
Registry listing for pitch-deck matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: pitch-deck is focused, and the summary matches what you get after install.
Useful defaults in pitch-deck — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added pitch-deck from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
pitch-deck fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend pitch-deck for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for pitch-deck matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: pitch-deck is the kind of skill you can hand to a new teammate without a long onboarding doc.
pitch-deck has been reliable in day-to-day use. Documentation quality is above average for community skills.
pitch-deck is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 30