fsi-strip-profile▌
anthropics/financial-services-plugins · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Data Sources:
Workflow
1. Clarify Requirements
- Ask the user: Single-slide or multi-slide (3-4 slides)?
- Ask the user: Any specific focus areas or topics to emphasize?
- Only after user confirms, proceed to research
2. Research & Planning
Data Sources:
- Primary: Company filings (BamSEC, SEC EDGAR - "Item 1. Business", MD&A), investor presentations, corporate website
- Market data: Bloomberg, FactSet, CapIQ (price, shares, market cap, net debt, EV, ownership)
- Estimates: FactSet/CapIQ consensus for NTM revenue, EBITDA, EPS
- News: Press releases from last 90 days, M&A activity, guidance changes
Required Metrics:
- Financials: Revenue, EBITDA, margins (%), EPS, FCF for ±3 years
- Valuation: Market Cap, EV, EV/Revenue, EV/EBITDA, P/E multiples
- Growth: YoY growth rates (%)
- Ownership: Top 5 shareholders with % ownership
- Segments: Product mix and/or geographic mix (% breakdown)
Normalization:
- Convert all amounts to consistent currency
- 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 -r 150 -f 1 -l 1 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.
Per quadrant targets:
- Company Overview: 6-8 bullets minimum (HQ, founded, employees, CEO/CFO, market cap, ticker, industry, key stat)
- Business & Positioning: 6-8 bullets (revenue drivers, products, market share %, competitive moat, customer count, geographic mix)
- Key Financials: Table with 8-10 rows OR chart + 4-5 key metrics (Revenue, EBITDA, margins, EPS, FCF, growth rates, valuation multiples)
- Fourth quadrant: 5-7 bullets (ownership %, recent M&A, developments, catalysts)
Information packing techniques:
- 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:
def add_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 paragraphs
for 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 bar slide.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 });Bullet formatting tips:
bullet: { indent: 10 }- controls bullet indentation (smaller = tighter)paraSpaceAfter: 6- space after each paragraph in points- Pack multiple related facts into each bullet (e.g., "HQ: Austin; Founded: 2003")
- Include specific numbers and percentages for information density
-
Title case for titles (not ALL CAPS), left-aligned
-
Consistent fonts everywhere including tables
-
Company's brand colors - YOU MUST research actual brand colors via web search before creating slides. Do not guess or assume colors.
-
Follow brand guidelines if provided
Visual Reference
See examples/Nike_Strip_Profile_Example.pptx for layout inspiration. Adapt colors to each company's brand.
First Page Layout
Must pass "30-second comprehension test" for a busy executive.
Slide Setup (CRITICAL)
Use 4:3 aspect ratio (standard IB pitch book format):
const pptx = new pptxgen();
pptx.layout = 'LAYOUT_4x3'; // 10" wide × 7.5" tall - MUST USE THIS
Slide Coordinate System
PptxGenJS uses inches. 4:3 slide = 10" wide × 7.5" tall.
- x: horizontal position from left edge (0 = left, 10 = right)
- y: vertical position from top edge (0 = top, 7.5 = bottom)
- Content must stay within bounds - leave 0.3" margin on all sides
First Page Positioning (in inches)
┌─────────────────────────────────────────────────────────────────┐
│ y=0.2 Title: Company Name (Ticker) │
├────────────────────────────┬────────────────────────────────────┤
│ y=0.6 Company Overview │ y=0.6 Business & Positioning │
│ x=0.3, w=4.7 │ x=5.0, w=4.7 │
│ h=3.0 │ h=3.0 │
├────────────────────────────┼────────────────────────────────────┤
│ y=3.7 Key Financials │ y=3.7 Stock/Recent Developments │
│ x=0.3, w=4.7 │ x=5.0, w=4.7 │
│ h=3.5 │ h=3.5 │
└────────────────────────────┴────────────────────────────────────┘
y=7.5
Title Section (y=0.2)
Company Name (Ticker) - Example: Tesla, Inc. (TSLA)
slide.addText('Tesla, Inc. (TSLA)', { x: 0.3, y: 0.2, how to use fsi-strip-profileHow to use fsi-strip-profile on Cursor
AI-first code editor with Composer
1Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add fsi-strip-profile
2Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
$npx skills add https://github.com/anthropics/financial-services-plugins --skill fsi-strip-profileThe skills CLI fetches fsi-strip-profile from GitHub repository anthropics/financial-services-plugins and configures it for Cursor.
3Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
◆ Which agents do you want to install to?││ ── Universal (.agents/skills) ── always included ────│ • Amp│ • Antigravity│ • Cline│ • Codex│ ●Cursor(selected)│ • Cursor│ • Windsurf4Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/fsi-strip-profileReload or restart Cursor to activate fsi-strip-profile. Access the skill through slash commands (e.g., /fsi-strip-profile) or your agent's skill management interface.
⚠Security & Verification 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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
Additional Resources
List & Monetize Your Skill
Submit your Claude Code skill and start earning
GET_STARTED →Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
✓Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›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
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share 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
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
general reviewsRatings
4.7★★★★★66 reviews- ★★★★★Ganesh Mohane· Dec 20, 2024
fsi-strip-profile fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Naina Sethi· Dec 20, 2024
fsi-strip-profile has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★William Smith· Dec 20, 2024
Keeps context tight: fsi-strip-profile is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Ira Srinivasan· Dec 16, 2024
fsi-strip-profile fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Lucas Rao· Dec 12, 2024
Useful defaults in fsi-strip-profile — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Omar Desai· Dec 8, 2024
fsi-strip-profile is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Naina Khanna· Dec 8, 2024
We added fsi-strip-profile from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Naina Reddy· Nov 27, 2024
Solid pick for teams standardizing on skills: fsi-strip-profile is focused, and the summary matches what you get after install.
- ★★★★★Ren Ghosh· Nov 27, 2024
fsi-strip-profile reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Sakshi Patil· Nov 11, 2024
Registry listing for fsi-strip-profile matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 66
1 / 7