earnings-competitive-review
Analyze management's discussion of competitive landscape, market positioning, and strategic differentiation from earnings call transcripts.
What this skill does
# Earnings Competitive Review Analyze management's discussion of competitive landscape, market positioning, and strategic differentiation from earnings call transcripts. ## Prerequisites Ensure Octagon MCP is configured. See [references/mcp-setup.md](references/mcp-setup.md) for installation instructions. ## Workflow ### Step 1: Extract Competitive Commentary Use the Octagon MCP to analyze competitive discussions: ``` Analyze management's discussion of competitive landscape and market positioning from <TICKER>'s earnings call. ``` ### Step 2: Targeted Competitive Analysis Focus on specific aspects of competitive positioning: ``` # Market Share What did management say about market share in <TICKER>'s earnings call? # Competitor Mentions Which competitors were mentioned in <TICKER>'s earnings call? # Differentiation How does management describe <TICKER>'s competitive differentiation? # Pricing Strategy What did management say about pricing and competition in <TICKER>'s call? # Product Positioning Analyze product competitive positioning from <TICKER>'s earnings call. # Segment Competition Extract competitive dynamics by segment from <TICKER>'s earnings transcript. ``` ## Expected Output The skill returns structured competitive analysis including: | Component | Description | |-----------|-------------| | Segment Analysis | Competitive position by business unit | | Key Differentiators | Stated competitive advantages | | Competitor References | Direct and indirect mentions | | Market Share Commentary | Position and trends | | Strategic Execution | Go-to-market approach | | Follow-up Questions | AI-generated questions for deeper research | | Source Citations | Transcript page references | ## Example Query ``` Analyze management's discussion of competitive landscape and market positioning from AMD's earnings call. ``` ## Example Response **AMD's Competitive Landscape and Market Positioning Strategy** AMD's management emphasizes a multi-pronged approach to maintaining competitiveness across key markets: **Data Center Segment** - Focus on total cost of ownership and performance efficiency (performance per watt/dollar) with EPYC processors, which have gained traction in cloud and enterprise sectors - Acknowledges competitive pressures but highlights advantages in advanced packaging and integration techniques **AI Market** - Aggressively expanding with products like the MI300, targeting the rapidly growing AI infrastructure segment - Positions itself as a leader in performance-per-dollar metrics to attract cloud and enterprise clients **Client Businesses** - Prioritizes performance efficiency to differentiate in a crowded market, leveraging product innovation and customer engagement **Strategic Execution** - Expanding product portfolios and optimizing go-to-market strategies to address both cloud and enterprise needs - Successfully gained server CPU market share while addressing inventory and supply chain challenges Management remains confident in their product roadmap and technological advantages, despite acknowledging competitive pressures from incumbents. **Follow-up Questions** - What specific market share gains has AMD achieved in server CPUs? - How does AMD quantify the performance-per-dollar advantage of EPYC processors? - What are the projected revenue contributions from AI products like MI300? **Sources**: AMD transcripts from Q1 2023 - Q2 2024, Pages: 6-10 ## Competitive Analysis Framework ### Market Position Categories | Position | Description | Example Language | |----------|-------------|------------------| | Leader | Dominant market share | "Industry leading," "market leader" | | Challenger | Gaining share aggressively | "Gaining traction," "taking share" | | Fast Follower | Quick to match leaders | "Competitive offering," "comparable" | | Niche Player | Focused positioning | "Specialized," "targeted segment" | | Declining | Losing share | "Competitive pressures," "challenged" | ### Competitive Advantage Types | Advantage Type | Examples | |----------------|----------| | Technology | IP, patents, R&D lead | | Cost | Scale, efficiency, sourcing | | Product | Features, performance, quality | | Distribution | Channel, reach, relationships | | Brand | Recognition, loyalty, premium | | Ecosystem | Partners, integrations, lock-in | ## Segment-Level Analysis ### Building Segment Competitive View | Segment | Position | Key Competitor | Advantage | Threat Level | |---------|----------|----------------|-----------|--------------| | Data Center | Challenger | Intel | Performance/watt | Medium | | AI/ML | Growing | NVIDIA | Price/performance | High | | Client PC | Stable | Intel, Qualcomm | Performance | Medium | ### Segment Dynamics | Signal | Bullish | Bearish | |--------|---------|---------| | Market Share | Gaining | Losing | | Win Rates | Improving | Declining | | Pricing Power | Maintained | Eroding | | Customer Wins | Announced | Silent | ## Competitor Mention Analysis ### Direct vs. Indirect References | Type | Example | Interpretation | |------|---------|----------------| | Direct Naming | "Compared to Intel..." | Confident positioning | | Indirect Reference | "Vs. incumbent..." | Cautious comparison | | Industry Reference | "Best in class..." | Avoiding direct conflict | | No Mention | Silence on competitor | May be avoiding topic | ### Competitor Mention Frequency | Frequency | Interpretation | |-----------|----------------| | Multiple mentions | Key competitive threat | | Single mention | Acknowledging presence | | No mentions | Either dominant or avoiding | | Defensive mentions | Addressing concerns | ## Differentiation Analysis ### Key Differentiator Categories | Category | AMD Examples | Intel Examples | |----------|--------------|----------------| | Performance | Performance per watt | Single-thread performance | | Value | TCO, price/performance | Ecosystem, support | | Technology | Chiplet architecture | Process node | | Ecosystem | Open standards | Integrated stack | ### Sustainability Assessment | Factor | Sustainable | Temporary | |--------|-------------|-----------| | Technology | Patents, years ahead | Quick to copy | | Cost | Structural advantage | One-time gain | | Brand | Built over time | Recent momentum | | Ecosystem | Lock-in effects | Easy to switch | ## Market Share Commentary ### Share Trend Analysis | Trend | Language Signals | |-------|------------------| | Gaining Share | "Win rates improving," "share gains" | | Holding Share | "Maintaining position," "stable" | | Losing Share | "Competitive pressure," "challenging" | | Share Silent | No mention of share trends | ### Quantifying Share Claims | Claim Type | Reliability | |------------|-------------| | Specific Numbers | High - verifiable | | Directional | Medium - need validation | | Qualitative Only | Low - interpretation needed | ## Strategic Execution Analysis ### Go-to-Market Signals | Signal | Interpretation | |--------|----------------| | New channel partners | Expanding reach | | Customer wins announced | Momentum building | | Product launches | Competitive response | | Pricing actions | Market dynamics | | Geographic expansion | Growth focus | ### Execution Confidence | Indicator | High Confidence | Low Confidence | |-----------|-----------------|----------------| | Specificity | Detailed examples | Vague claims | | Timeline | Clear milestones | "Over time" | | Metrics | Quantified results | Qualitative only | | Consistency | Matches prior quarters | Changing narrative | ## Use Cases 1. **Competitive Intelligence**: Understand positioning vs. peers 2. **Investment Thesis**: Validate competitive moat 3. **Risk Assessment**: Identify competitive threats 4. **Sector Analysis**: Compare across industry players 5. **Due Diligence**: Comprehensive competitive review 6. **Trend Tracking**: Monitor positioning changes over time ## Combining with Other Skills | Skill | Combined Analysis | |-------|---------------
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.