Confirm successful installation by checking the skill directory location:
.cursor/skills/fsi-strip-profile
Restart Cursor to activate fsi-strip-profile. Access via /fsi-strip-profile 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.
Scale consistently ($mm or $bn throughout, not mixed)
Before Building:
Print outline to chat with 4-5 bullet points per item (actual numbers, no placeholders)
Print style choices: fonts, colors (hex codes), chart types for each data set
Get user alignment: "Does this outline and visual strategy align with your vision?"
3. Slide-by-Slide Creation
CRITICAL: You MUST create ONE slide at a time and get user approval before proceeding to the next slide.
For EACH slide:
Create ONLY this one slide with PptxGenJS
MANDATORY: Convert to image for review - You MUST convert slides to images so you can visually verify them:
soffice --headless --convert-to pdf presentation.pptx
pdftoppm -jpeg-r150-f1-l1 presentation.pdf slide
MANDATORY VISUAL REVIEW: You MUST carefully examine the rendered slide image before proceeding:
Text overlap check: Scan every text element - do any labels, bullets, or titles collide with each other?
Text cutoff check: Is any text truncated at boundaries? Are all words fully visible?
Chart boundary check: Do charts stay within their containers? Are ALL axis labels fully visible?
Quadrant integrity: Does content in one quadrant bleed into adjacent quadrants?
If ANY overlap or cutoff is detected: Fix immediately using these strategies in order:
First: Reduce font size (go down 1-2pt)
Second: Shorten text (abbreviate, remove less critical info)
Third: Adjust element positions or container sizes
Re-render and verify again - do not proceed until all text fits cleanly
Show slide image to user with download link
STOP and wait for explicit user approval before creating the next slide. Do NOT proceed until user confirms.
YOU MUST CHECK FOR THESE SPECIFIC ISSUES ON EVERY PAGE:
Table rows colliding with text below them
Chart x-axis labels cut off at bottom
Long bullet points wrapping into adjacent content
Quadrant content bleeding into adjacent quadrants
Title text overlapping with content below
Legend text overlapping with chart elements
Footer/source text colliding with main content
Slide Format Requirements
Information Density is Critical
The #1 goal is MAXIMUM information density. A busy executive should understand the entire company story in 30 seconds. Fill every quadrant to capacity.
Combine related facts: "HQ: Austin, TX; Founded: 2003; 140K employees"
Always include numbers: "$50B revenue" not "large revenue"
Add context: "EBITDA margin: 25% (vs. 18% industry avg)"
Include YoY changes: "Revenue: $125M (+28% YoY)"
Use percentages: "Enterprise: 62% of revenue"
If a quadrant looks sparse, add more:
Segment breakdowns with %
Geographic revenue splits
Customer concentration (top 10 = X%)
Recent contract wins with $ values
Guidance vs. consensus
Insider ownership %
Line spacing - use single textbox per section:
defadd_section(slide, x, y, w, header_text, bullets, header_size=10, bullet_size=8):"""Header + bullets in single textbox with natural spacing""" tb = slide.shapes.add_textbox(x, y, w, Inches(len(bullets)*0.18+0.3)) tf = tb.text_frame
tf.word_wrap =True# Header paragraph p = tf.paragraphs[0] p.text = header_text
p.font.bold =True p.font.size = Pt(header_size) p.font.color.rgb = RGBColor(0,51,102) p.space_after = Pt(6)# Small gap after header# Bullet paragraphsfor bullet in bullets: p = tf.add_paragraph() p.text = bullet
p.font.size = Pt(bullet_size) p.space_after = Pt(3)return tb
Key spacing principles:
Put header + bullets in SAME textbox (no separate header textbox)
Use space_after = Pt(6) after header, Pt(3) between bullets
Don't hardcode gaps - let paragraph spacing handle it naturally
If content overflows, reduce font by 1pt rather than removing content
3-4 dense slides - use quadrants, columns, tables, charts
Bullets for ALL body text - NEVER paragraphs. Use ONE textbox per section with all bullets inside - do NOT create separate textboxes for each bullet point. Use PptxGenJS bullet formatting:
// CORRECT: Single textbox with bullet list - each array item becomes a bullet// Position in top-left quadrant (Company Overview) - after header with accent barslide.addText([{text:'Headquarters: Austin, Texas; Founded 2003',options:{bullet:{indent:10},breakLine:true}},{text:'Employees: 140,000+ globally across 6 continents',options:{bullet:{indent:10},breakLine:true}},{text:'CEO: Elon Musk; CFO: Vaibhav Taneja',options:{bullet:{indent:10},breakLine:true}},{text:'Market Cap: $850B (#6 globally by market cap)',options:{bullet:{indent:10},breakLine:true}},{text:'Segments: Automotive (85%), Energy (10%), Services (5%)',options:{bullet:{indent:10}}}],{x:0.45,y:0.95,w:4.5,h:2.6,fontSize:11,fontFace:'Arial',valign:'top',paraSpaceAfter:6});// WRONG: Multiple separate textboxes for each bullet - causes alignment issues// slide.addText('Headquarters: Austin', { x: 0.5, y: 1.0, bullet: true });
βΊ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