skills/bellabe/foundations-market-intelligence/SKILL.md
Market analysis and competitive intelligence for startups. Use when analyzing market opportunities, sizing TAM, profiling segments, or mapping competition.
npx skillsauth add aiskillstore/marketplace foundations-market-intelligenceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The Market Intelligence Agent provides comprehensive market analysis for startup decision-making. This agent merges four specialized capabilities: Context Mapping, Opportunity Evaluation, Segment Profiling, and Competitor Intelligence into a unified workflow that produces actionable market insights.
Primary Use Cases: Market discovery, TAM/SAM/SOM analysis, competitive assessment, customer segmentation, opportunity scoring, market timing evaluation.
Lifecycle Phases: Discovery (primary), quarterly reviews, major pivots, expansion planning.
Calculate addressable market using rigorous bottom-up and top-down methodologies.
Workflow:
Define Market Boundaries
Calculate TAM (Total Addressable Market)
Calculate SAM (Serviceable Addressable Market)
Calculate SOM (Serviceable Obtainable Market)
Segment the Market
Validate Segment Viability
Output Template:
Market Size Analysis
├── TAM: $XXM - $XXXM (methodology: top-down + bottom-up)
├── SAM: $XXM - $XXM (X% of TAM, constraints: geography, channels)
├── SOM (Year 1-3): $XM - $XXM (X% market share assumption)
└── Confidence Level: High/Medium/Low (rationale)
Top 3 Segments (prioritized):
1. [Segment Name]
- Size: X customers / $XXM market
- Pain Severity: X/5
- Urgency: X/5
- Accessibility: [channels]
- Willingness to Pay: $X-$X per [unit]
2. [Segment Name]...
3. [Segment Name]...
Penetration Strategy:
- Entry segment: [Segment 1]
- Expansion path: [Segment 1] → [Segment 2] → [Segment 3]
- Rationale: [why this sequence]
Map the competitive landscape to identify differentiation opportunities and strategic positioning.
Workflow:
Identify Competitors
Analyze Competitive Positioning
Map Feature Gaps
Assess Go-to-Market Strategies
Track Strategic Activity
Identify Differentiation Opportunities
Output Template:
Competitive Matrix
| Competitor | Positioning | Strengths | Weaknesses | Pricing | Funding |
|------------|-------------|-----------|------------|---------|---------|
| [Name 1] | [1 line] | [3 max] | [3 max] | $X/mo | $XM |
| [Name 2] | [1 line] | [3 max] | [3 max] | $X/mo | $XM |
| ... | | | | | |
Differentiation Opportunities:
1. [Opportunity]: [Description + rationale]
2. [Opportunity]: [Description + rationale]
3. [Opportunity]: [Description + rationale]
Competitive Threats:
- Immediate: [threat + mitigation strategy]
- Medium-term: [threat + monitoring plan]
- Long-term: [threat + strategic positioning]
Recommended Positioning:
[1-2 sentences describing unique strategic position]
Deep research into target customer problems, buying behavior, and decision criteria.
Workflow:
Research Pain Points
Define Ideal Customer Profile (ICP)
Create Personas
Quantify Problem & Solution Value
Map Buying Process
Output Template:
Ideal Customer Profile (ICP)
[B2B Example]
├── Company Size: X-X employees
├── Revenue: $XM-$XM ARR
├── Industry: [primary], [secondary]
├── Growth Stage: [seed/series A/B/growth]
├── Tech Stack: [key technologies]
└── Buying Authority: [role/title]
Primary Persona: [Name/Title]
├── Goals: [3 key objectives]
├── Challenges: [3 main pain points]
├── Daily Context: [typical day/workflow]
├── Information Sources: [where they learn]
├── Objections: [typical concerns]
└── Success Metrics: [how they measure results]
Anti-Persona: [Who NOT to target]
- [Profile]: [reason to avoid]
Customer Acquisition Strategy:
├── Entry Point: [specific pain point to lead with]
├── Value Proof: [how to demonstrate value quickly]
├── Buying Triggers: [events that create urgency]
└── First Purchase: [initial offering to convert]
Problem-Solution Economics:
├── Annual Cost of Problem: $X per customer
├── Solution Value Delivery: $X per customer per year
├── Value-to-Price Ratio: Xx (target: >10x for early stage)
└── Payback Period: X months
Assess market growth, trends, and timing to evaluate entry strategy and readiness.
Workflow:
Assess Market Growth
Identify Consolidation Trends
Detect Disruption Signals
Evaluate Market Readiness
Assess Category Creation vs. Category Entry
Output Template:
Market Dynamics Assessment
Growth Profile:
├── Historical CAGR: X% (20XX-20XX)
├── Projected CAGR: X% (20XX-20XX)
├── Growth Stage: [emerging/growth/mature/declining]
└── Growth Drivers: [3 key factors]
Market Structure:
├── Concentration: [fragmented/consolidating/oligopoly]
├── Recent M&A: [X acquisitions in past 2 years]
├── Market Leader Share: X%
└── Defensibility: [network effects/switching costs/brand/other]
Disruption Signals:
├── Technology: [enabling technology shifts]
├── Regulatory: [policy changes affecting market]
├── Cultural: [behavioral or preference shifts]
└── Economic: [macro factors]
Market Timing Assessment:
├── Timing Score: X/100
├── Adoption Phase: [innovators/early adopters/early majority/late majority]
├── Market Readiness: [too early/right time/too late]
└── Rationale: [2-3 sentences]
Entry Strategy:
├── Approach: [category creation/category entry]
├── Positioning: [how to frame the solution]
├── Education Required: [low/medium/high]
└── Timing Recommendation: [now/wait X months/conditions to meet]
Synthesize all intelligence into a comprehensive go/no-go recommendation.
Workflow:
Evaluate Market Attractiveness
Assess Competitive Intensity
Evaluate Execution Fit
Risk Assessment
Prioritize Opportunities
Generate Recommendation
Output Template:
Opportunity Scoring Summary
Overall Score: XX/100 (Recommendation: GO / NO-GO / INVESTIGATE FURTHER)
Component Scores:
├── Market Attractiveness: XX/100 (weight: 30%)
│ ├── Size & Growth: X/25
│ ├── Economics: X/25
│ ├── Accessibility: X/25
│ └── Timing: X/25
├── Competitive Position: XX/100 (weight: 35%)
│ ├── Differentiation Potential: X/35
│ ├── Barriers to Entry: X/35
│ └── Competitive Intensity: X/30
└── Execution Fit: XX/100 (weight: 35%)
├── Team/Expertise: X/35
├── Resources Available: X/35
└── Strategic Alignment: X/30
Risk Assessment:
├── CRITICAL RISKS (kill if not mitigated):
│ - [Risk]: [Mitigation approach]
├── HIGH RISKS (monitor closely):
│ - [Risk]: [Mitigation approach]
└── MEDIUM RISKS (acceptable):
- [Risk]: [Mitigation approach]
Key Assumptions to Validate:
1. [Assumption]: [Validation method]
2. [Assumption]: [Validation method]
3. [Assumption]: [Validation method]
Recommended Next Actions:
1. [Action]: [Expected outcome + timeline]
2. [Action]: [Expected outcome + timeline]
3. [Action]: [Expected outcome + timeline]
Confidence Level: X% (rationale: [1-2 sentences])
To perform comprehensive market intelligence analysis, provide:
Required:
product_idea: Brief description (1-2 sentences) of what you're buildingtarget_geography: List of countries/regions to analyzeindustry_vertical: Primary industry or categoryOptional:
initial_hypothesis: Your assumptions about market, customer, competitionconstraints: Budget, timeline, team size limitationsstrategic_context: Company goals, pivoting from what, expansion plansExample Input:
product_idea: "AI-powered beauty product recommendations based on skin analysis and personal preferences"
target_geography: ["United States", "Canada"]
industry_vertical: "Beauty & Personal Care - Digital/D2C"
initial_hypothesis: {
"target_customer": "Women 25-40, digitally native, skincare enthusiasts",
"willingness_to_pay": "$15-30/month subscription",
"main_competitor": "Sephora's Color IQ, Function of Beauty"
}
All market intelligence analysis follows this standardized format:
{
"market_size": {
"TAM": 5000000000,
"SAM": 1200000000,
"SOM": 24000000,
"confidence": "medium",
"methodology": "bottom-up + top-down validated"
},
"top_segments": [
{
"name": "Skincare Enthusiasts (25-40)",
"size": 12000000,
"pain_severity": 4,
"urgency": 3,
"accessibility": "high",
"willingness_to_pay": "$20-35/month"
},
{
"name": "Beauty Novices Seeking Guidance",
"size": 8500000,
"pain_severity": 3,
"urgency": 2,
"accessibility": "medium",
"willingness_to_pay": "$10-20/month"
},
{
"name": "Professional MUAs & Estheticians",
"size": 450000,
"pain_severity": 5,
"urgency": 4,
"accessibility": "medium",
"willingness_to_pay": "$50-100/month"
}
],
"competitors": [
{
"name": "Function of Beauty",
"positioning": "Personalized haircare via quiz",
"strengths": ["Strong brand", "Proven unit economics", "Wide distribution"],
"gaps": ["Limited to hair", "No AI/skin analysis", "High price point"],
"pricing": "$30-50/month",
"funding": "$150M Series C"
}
],
"market_timing": {
"score": 78,
"rationale": "AI beauty tech awareness high post-2023, but market not saturated. Early majority adoption phase. Strong timing.",
"recommendation": "Enter now"
},
"next_actions": [
"Validate willingness-to-pay with 20 customer interviews in primary segment",
"Build competitive feature matrix and identify 3 key differentiation points",
"Run micro-landing page test to validate demand ($500 budget, 2 weeks)"
]
}
problem-solution-fit: Market insights inform which problems to prioritize
value-proposition: Market positioning informs value articulation
business-model: Market economics drive business model design
go-to-market: Market intelligence shapes channel strategy
validation: Experiment results refine market assumptions
execution: Actual user data improves intelligence accuracy
Market Sizing Errors:
Competitive Analysis Errors:
Customer Intelligence Errors:
Market Timing Errors:
User Request: "Analyze the market for AI-powered personal finance coaching for Gen Z"
Agent Process:
Output: Complete market intelligence report with recommended entry segment and next 3 actions
User Request: "Update our market intelligence - we launched 6 months ago, seeing traction in enterprise segment"
Agent Process:
Output: Updated market intelligence focusing on changes and new opportunities
User Request: "We're struggling in B2C, should we pivot to B2B SaaS?"
Agent Process:
Output: Comparative market analysis with pivot recommendation and de-risking actions
Track these metrics to ensure market intelligence effectiveness:
Accuracy: How often do market size estimates match reality? (Target: ±30%) Usefulness: Do other agents use this intelligence in their work? (Target: >80% utilization) Freshness: How often is intelligence updated? (Target: Quarterly minimum) Action Orientation: Do intelligence reports lead to clear next actions? (Target: 100%)
Run this checklist every quarter to keep intelligence current:
This agent transforms raw market data into strategic intelligence, enabling informed decisions about market entry, positioning, and resource allocation.
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.