comps-analysis▌
anthropics/financial-services-plugins · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
ALWAYS follow this data source hierarchy:
Comparable Company Analysis
⚠️ CRITICAL: Data Source Priority (READ FIRST)
ALWAYS follow this data source hierarchy:
- FIRST: Check for MCP data sources - If S&P Kensho MCP, FactSet MCP, or Daloopa MCP are available, use them exclusively for financial and trading information
- DO NOT use web search if the above MCP data sources are available
- ONLY if MCPs are unavailable: Then use Bloomberg Terminal, SEC EDGAR filings, or other institutional sources
- NEVER use web search as a primary data source - it lacks the accuracy, audit trails, and reliability required for institutional-grade analysis
Why this matters: MCP sources provide verified, institutional-grade data with proper citations. Web search results can be outdated, inaccurate, or unreliable for financial analysis.
Overview
This skill teaches Claude to build institutional-grade comparable company analyses that combine operating metrics, valuation multiples, and statistical benchmarking. The output is a structured Excel/spreadsheet that enables informed investment decisions through peer comparison.
Reference Material & Contextualization:
An example comparable company analysis is provided in examples/comps_example.xlsx. When using this or other example files in this skill directory, use them intelligently:
DO use examples for:
- Understanding structural hierarchy (how sections flow)
- Grasping the level of rigor expected (statistical depth, documentation standards)
- Learning principles (clear headers, transparent formulas, audit trails)
DO NOT use examples for:
- Exact reproduction of format or metrics
- Copying layout without considering context
- Applying the same visual style regardless of audience
ALWAYS ask yourself first:
- "Do you have a preferred format or should I adapt the template style?"
- "Who is the audience?" (Investment committee, board presentation, quick reference, detailed memo)
- "What's the key question?" (Valuation, growth analysis, competitive positioning, efficiency)
- "What's the context?" (M&A evaluation, investment decision, sector benchmarking, performance review)
Adapt based on specifics:
- Industry context: Big tech mega-caps need different metrics than emerging SaaS startups
- Sector-specific needs: Add relevant metrics early (e.g., cloud ARR, enterprise customers, developer ecosystem for tech)
- Company familiarity: Well-known companies may need less background, more focus on delta analysis
- Decision type: M&A requires different emphasis than ongoing portfolio monitoring
Core principle: Use template principles (clear structure, statistical rigor, transparent formulas) but vary execution based on context. The goal is institutional-quality analysis, not institutional-looking templates.
User-provided examples and explicit preferences always take precedence over defaults.
Core Philosophy
"Build the right structure first, then let the data tell the story."
Start with headers that force strategic thinking about what matters, input clean data, build transparent formulas, and let statistics emerge automatically. A good comp should be immediately readable by someone who didn't build it.
⚠️ CRITICAL: Formulas Over Hardcodes + Step-by-Step Verification
Environment — Office JS vs Python:
- If running inside Excel (Office Add-in / Office JS): Use Office JS directly (
Excel.run(async (context) => {...})). Write formulas viarange.formulas = [["=E7/C7"]], notrange.values. No separate recalc step — Excel handles it natively. Userange.format.*for colors/fonts. - If generating a standalone .xlsx file: Use Python/openpyxl. Write
cell.value = "=E7/C7"(formula string). - Same principles either way — just translate the API calls.
- Office JS merged cell pitfall: Do NOT call
.merge()then set.valueson the merged range (throwsInvalidArgument— range still reports its pre-merge dimensions). Instead write the value to the top-left cell alone, then merge + format the full range:ws.getRange("A1").values = [["TECHNOLOGY — COMPARABLE COMPANY ANALYSIS"]]; const hdr = ws.getRange("A1:H1"); hdr.merge(); hdr.format.fill.color = "#1F4E79"; hdr.format.font.color = "#FFFFFF"; hdr.format.font.bold = true;
Formulas, not hardcodes:
- Every derived value (margin, multiple, statistic) MUST be an Excel formula referencing input cells — never a pre-computed number pasted in
- When using Python/openpyxl to build the sheet: write
cell.value = "=E7/C7"(formula string), NOTcell.value = 0.687(computed result) - The only hardcoded values should be raw input data (revenue, EBITDA, share price, etc.) — and every one of those gets a cell comment with its source
- Why: the model must update automatically when an input changes. A hardcoded margin is a silent bug waiting to happen.
Verify step-by-step with the user:
- After setting up the structure → show the user the header layout before filling data
- After entering raw inputs → show the user the input block and confirm sources/periods before building formulas
- After building operating metrics formulas → show the calculated margins and sanity-check with the user before moving to valuation
- After building valuation multiples → show the multiples and confirm they look reasonable before adding statistics
- Do NOT build the entire sheet end-to-end and then present it — catch errors early by confirming each section
Section 1: Document Structure & Setup
Header Block (Rows 1-3)
Row 1: [ANALYSIS TITLE] - COMPARABLE COMPANY ANALYSIS
Row 2: [List of Companies with Tickers] • [Company 1 (TICK1)] • [Company 2 (TICK2)] • [Company 3 (TICK3)]
Row 3: As of [Period] | All figures in [USD Millions/Billions] except per-share amounts and ratios
Why this matters: Establishes context immediately. Anyone opening this file knows what they're looking at, when it was created, and how to interpret the numbers.
Visual Convention Standards (OPTIONAL - User preferences and uploaded templates always override)
IMPORTANT: These are suggested defaults only. Always prioritize:
- User's explicit formatting preferences
- Formatting from any uploaded template files
- Company/team style guides
- These defaults (only if no other guidance provided)
Suggested Font & Typography:
- Font family: Times New Roman (professional, readable, industry standard)
- Font size: 11pt for data cells, 12pt for headers
- Bold text: Section headers, company names, statistic labels
Default Color & Shading — Professional Blue/Grey Palette (minimal is better):
- Keep it restrained — only blues and greys. Do NOT introduce greens, oranges, reds, or multiple accent colors. A clean comps sheet uses 3-4 colors total.
- Section headers (e.g., "OPERATING STATISTICS & FINANCIAL METRICS"):
- Dark blue background (
#1F4E79or#17365Dnavy) - White bold text
- Full row shading across all columns
- Dark blue background (
- Column headers (e.g., "Company", "Revenue", "Margin"):
- Light blue background (
#D9E1F2or similar pale blue) - Black bold text
- Centered alignment
- Light blue background (
- Data rows:
- White background for company data
- Black text for formulas; blue text for hardcoded inputs
- Statistics rows (Maximum, 75th Percentile, etc.):
- Light grey background (
#F2F2F2) - Black text, left-aligned labels
- Light grey background (
- That's the whole palette: dark blue + light blue + light grey + white. Nothing else unless the user's template says otherwise.
Suggested Formatting Conventions:
- Decimal precision:
- Percentages: 1 decimal (12.3%)
- Multiples: 1 decimal (13.5x)
- Dollar amounts: No decimals, thousands separator (69,632)
- Margins shown as percentages: 1 decimal (68.7%)
- Borders: No borders (clean, minimal appearance)
- Alignment: All metrics center-aligned for clean, uniform appearance
- Cell dimensions: All column widths should be uniform/even, all row heights should be consistent (creates clean, professional grid)
Note: If the user provides a template file or specifies different formatting, use that instead.
Section 2: Operating Statistics & Financial Metrics
Core Columns (Start with these)
- Company - Names with consistent formatting
- Revenue - Size metric (can be LTM, quarterly, or annual depending on context)
- Revenue Growth - Year-over-year percentage change
- Gross Profit - Revenue minus cost of goods sold
- Gross Margin - GP/Revenue (fundamental profitability)
- EBITDA - Earnings before interest, tax, depreciation, amortization
- EBITDA Margin - EBITDA/Revenue (operating efficiency)
Optional Additions (Choose based on industry/purpose)
- Quarterly vs LTM - Include both if seasonality matters
- Free Cash Flow - For capital-intensive or SaaS businesses
- FCF Margin - FCF/Revenue (cash generation efficiency)
- Net Income - For mature, profitable companies
- Operating Income - For businesses with varying D&A
- CapEx metrics - For asset-heavy industries
- Rule of 40 - Specifically for SaaS (Growth % + Margin %)
- FCF Conversion - For quality of earnings analysis (advanced)
Formula Examples (Using Row 7 as example)
// Core ratios - these are always calculated
Gross Margin (F7): =E7/C7
EBITDA Margin (H7): =G7/C7
// Optional ratios - include if relevant
FCF Margin: =[FCF]/[Revenue]
Net Margin: =[Net Income]/[Revenue]
Rule of 40: =[Growth %]+[FCF Margin %]
Golden Rule: Every ratio should be [Something] / [Revenue] or [Something] / [Something from this sheet]. Keep it simple.
Statistics Block (After company data)
CRITICAL: Add statistics formulas for all comparable metrics (ratios, margins, growth rates, multiples).
[Leave one blank row for visual separation]
- Maximum: =MAX(B7:B9)
- 75th Percentile: =QUARTILE(B7:B9,3)
- Median: =MEDIAN(B7:B9)
- 25th Percentile: =QUARTILE(B7:B9,1)
- Minimum: =MIN(B7:B9)
Columns that NEED statistics (comparable metrics):
- Revenue Growth %, Gross Margin %, EBITDA Margin %, EPS
- EV/Revenue, EV/EBITDA, P/E, Dividend Yield %, Beta
Columns that DON'T need statistics (size metrics):
- Revenue, EBITDA, Net Income (absolute size varies by company scale)
- Market Cap, Enterprise Value (not comparable across different-sized companies)
Note: Add one blank row between company data and statistics rows for visual separation. Do NOT add a "SECTOR STATISTICS" or "VALUATION STATISTICS" header row.
Why quartiles matter: They show distribution, not just average. A 75th percentile multiple tells you what "premium" companies trade at.
Section 3: Valuation Multiples & Investment Metrics
Core Valuation Columns (Start with these)
- Company - Same order as operating section
- Market Cap - Current market valuation
- Enterprise Value - Market Cap ± Net Debt/Cash
- EV/Revenue - How much market pays per dollar of sales
- EV/EBITDA - How much market pays per dollar of earnings
- P/E Ratio - Price relative to net earnings
Optional Valuation Metrics (Choose based on context)
- FCF Yield - FCF/Market Cap (for cash-focused analysis)
- PEG Ratio - P/E/Growth Rate (for growth companies)
- Price/Book - Market value vs. book value (for asset-heavy businesses)
- ROE/ROA - Return metrics (for profitability comparison)
- Revenue/EBITDA CAGR - Historical growth rates (for trend analysis)
- Asset Turnover - Revenue/Assets (for operational efficiency)
- Debt/Equity - Leverage (for capital structure analysis)
Key Principle: Include 3-5 core multiples that matter for your industry. Don't include every possible metric just because you can.
Formula Examples
// Core multiples - always include these
EV/Revenue: =[Enterprise Value]/[LTM Revenue]
EV/EBITDA: =[Enterprise Value]/[LTM EBITDA]
P/E Ratio: =[Market Cap]/[Net Income]
// Optional multiples - include if data available
FCF Yield: =[LTM FCF]/[Market Cap]
PEG Ratio: =[P/E]/[Growth Rate %]
Cross-Reference Rule
CRITICAL: Valuation multiples MUST reference the operating metrics section. Never input the same raw data twice. If revenue is in C7, then EV/Revenue formula should reference C7.
Statistics Block
Same structure as operating section: Max, 75th, Median, 25th, Min for every metric. Add one blank row for visual separation between company data and statistics. Do NOT add a "VALUATION STATISTICS" header row.
Section 4: Notes & Methodology Documentation
Required Components
Data Sources & Quality:
- Where did the data come from? (S&P Kensho MCP, FactSet MCP, Daloopa MCP, Bloomberg, SEC filings)
- What period does it cover? (Q4 2024, audited figures)
- How was it verified? (Cross-checked against 10-K/10-Q)
- Note: Prioritize MCP data sources (S&P Kensho, FactSet, Daloopa) if available for better accuracy and traceability
Key Definitions:
- EBITDA calculation method (Gross Profit + D&A, or Operating Income + D&A)
- Free Cash Flow formula (Operating CF - CapEx)
- Special metrics explained (Rule of 40, FCF Conversion)
- Time period definitions (LTM, CAGR calculation periods)
Valuation Methodology:
- How was Enterprise Value calculated? (Market Cap + Net Debt)
- What growth rates were used? (Historical CAGR, forward estimates)
- Any adjustments made? (One-time items excluded, normalized margins)
Analysis Framework:
- What's the investment thesis? (Cloud/SaaS efficiency)
- What metrics matter most? (Cash generation, capital efficiency)
- How should readers interpret the statistics? (Quartiles provide context)
Section 5: Choosing the Right Metrics (Decision Framework)
Start with "What question am I answering?"
"Which company is undervalued?" → Focus on: EV/Revenue, EV/EBITDA, P/E, Market Cap → Skip: Operational details, growth metrics
"Which company is most efficient?" → Focus on: Gross Margin, EBITDA Margin, FCF Margin, Asset Turnover → Skip: Size metrics, absolute dollar amounts
"Which company is growing fastest?" → Focus on: Revenue Growth %, EBITDA CAGR, User/Customer Growth → Skip: Margin metrics, leverage ratios
"Which is the best cash generator?" → Focus on: FCF, FCF Margin, FCF Conversion, CapEx intensity → Skip: EBITDA, P/E ratios
Industry-Specific Metric Selection
Software/SaaS: Must have: Revenue Growth, Gross Margin, Rule of 40 Optional: ARR, Net Dollar Retention, CAC Payback Skip: Asset Turnover, Inventory metrics
Manufacturing/Industrials: Must have: EBITDA Margin, Asset Turnover, CapEx/Revenue Optional: ROA, Inventory Turns, Backlog Skip: Rule of 40, SaaS metrics
Financial Services: Must have: ROE, ROA, Efficiency Ratio, P/E Optional: Net Interest Margin, Loan Loss Reserves Skip: Gross Margin, EBITDA (not meaningful for banks)
Retail/E-commerce: Must have: Revenue Growth, Gross Margin, Inventory Turnover Optional: Same-Store Sales, Customer Acquisition Cost Skip: Heavy R&D or CapEx metrics
The "5-10 Rule"
5 operating metrics - Revenue, Growth, 2-3 margins/efficiency metrics 5 valuation metrics - Market Cap, EV, 3 multiples = 10 total columns - Enough to tell the story, not so many you lose the thread
If you have more than 15 metrics, you're probably including noise. Edit ruthlessly.
Section 6: Best Practices & Quality Checks
Before You Start
- Define the peer group - Companies must be truly comparable (similar business model, scale, geography)
- Choose the right period - LTM smooths seasonality; quarterly shows trends
- Standardize units upfront - Millions vs. billions decision affects everything
- Map data sources - Know where each number comes from
As You Build
-
Input all raw data first - Complete the blue text before writing formulas
-
Add cell comments to ALL hard-coded inputs - Right-click cell → Insert Comment → Document source OR assumption
For sourced data, cite exactly where it came from:
- Example: "Bloomberg Terminal - MSFT Equity DES, accessed 2024-10-02"
- Example: "Q4 2024 10-K filing, page 42, line item 'Total Revenue'"
- Example: "FactSet consensus estimate as of 2024-10-02"
- Include hyperlinks when possible: Right-click cell → Link → paste URL to SEC filing, data source, or report
For assumptions, explain the reasoning:
- Example: "Assumed 15% EBITDA margin based on peer median, company does not disclose"
- Example: "Estimated Enterprise Value as Market Cap + $50M net debt (from Q3 balance sheet, Q4 not yet available)"
- Example: "Forward P/E based on street consensus EPS of $3.45 (average of 12 analyst estimates)"
Why this matters: Enables audit trails, data verification, assumption transparency, and future updates
-
Build formulas row by row - Test each calculation before moving on
-
Use absolute references for headers - $C$6 locks the header row
-
Format consistently - Percentages as percentages, not decimals
-
Add conditional formatting - Highlight outliers automatically
Sanity Checks
- Margin test: Gross margin > EBITDA margin > Net margi
How to use comps-analysis on Cursor
AI-first code editor with Composer
Prerequisites
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 comps-analysis
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches comps-analysis from GitHub repository anthropics/financial-services-plugins and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate comps-analysis. Access the skill through slash commands (e.g., /comps-analysis) 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.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
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.
Ratings
4.8★★★★★31 reviews- ★★★★★Daniel Mensah· Dec 28, 2024
I recommend comps-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Michael White· Dec 28, 2024
Keeps context tight: comps-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Ganesh Mohane· Dec 24, 2024
comps-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Liam Lopez· Dec 16, 2024
Useful defaults in comps-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Fatima Srinivasan· Nov 19, 2024
comps-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Sakshi Patil· Nov 15, 2024
Registry listing for comps-analysis matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kofi Abebe· Nov 15, 2024
Keeps context tight: comps-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Tariq Ndlovu· Oct 10, 2024
Solid pick for teams standardizing on skills: comps-analysis is focused, and the summary matches what you get after install.
- ★★★★★Chaitanya Patil· Oct 6, 2024
comps-analysis reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Piyush G· Sep 25, 2024
I recommend comps-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 31