skills/market-analyzer/SKILL.md
Structured market analysis with TAM/SAM/SOM sizing, trends, and competitive landscape via WebSearch, producing investor-grade cited reports. Triggers on: "market size", "TAM SAM SOM", "market opportunity", "industry analysis", "how big is the market", "market trends". NOT for financial modeling or pricing.
npx skillsauth add mathews-tom/armory market-analyzerInstall 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.
Produces structured market analysis reports: sizes the addressable market using top-down and bottom-up methods, identifies growth trajectories and adoption stages, segments customers, and assesses timing. Every estimate cites a data source or states its assumption explicitly.
| File | Contents | Load When |
| ------------------------------ | ------------------------------------------------------------------ | --------- |
| references/tam-sam-som.md | TAM/SAM/SOM definitions, calculation formulas, common mistakes | Always |
| references/trend-analysis.md | Trend categorization framework, adoption lifecycle, timing signals | Always |
| references/market-sizing.md | Data sources, estimation techniques, confidence framework | Always |
Use WebSearch to gather quantitative market data:
For each data point, record the source, publication date, and methodology (if available).
Apply both estimation approaches and cross-validate:
Top-down (from total industry):
TAM = Total industry revenue or total potential buyers x average revenue per buyer
SAM = TAM x % addressable by geography, segment, and channel
SOM = SAM x realistic capture rate (year 1-3)
Bottom-up (from unit economics):
Reachable customers = Identified target accounts or users in reachable channels
SOM = Reachable customers x conversion rate x average revenue per customer
SAM = SOM scaled to full serviceable segment (remove channel constraints)
TAM = SAM scaled to total market (remove geographic/segment constraints)
Cross-validate the two approaches. If they diverge by more than 3x, investigate the discrepancy and document the reason.
Evaluate four dimensions:
Identify 2-5 distinct customer segments:
Produce the structured output below.
## Market Analysis: {Subject}
### Executive Summary
**Market Opportunity Score: {1-5}/5**
{2-3 sentence summary of the opportunity, key market size, and timing assessment.}
### TAM / SAM / SOM
| Level | Value | Methodology | Confidence |
|-------|-------|-------------|------------|
| TAM | ${amount} | {Top-down / Bottom-up / Both} | {High/Medium/Low} |
| SAM | ${amount} | {methodology summary} | {High/Medium/Low} |
| SOM (Year 1) | ${amount} | {methodology summary} | {High/Medium/Low} |
| SOM (Year 3) | ${amount} | {methodology summary} | {High/Medium/Low} |
**Top-down calculation:**
{Step-by-step derivation with sources}
**Bottom-up calculation:**
{Step-by-step derivation with sources}
**Cross-validation:**
{Comparison of approaches, explanation of any divergence}
### Market Trends
| Dimension | Assessment | Evidence |
|-----------|-----------|----------|
| Growth trajectory | {Emerging/Growing/Mature/Declining} | {CAGR, data source} |
| Adoption stage | {Innovators/Early Adopters/Early Majority/Late Majority} | {penetration %, signal} |
| Regulatory | {Tailwind/Neutral/Headwind} | {specific regulation or policy} |
| Macro trends | {Favorable/Mixed/Unfavorable} | {key trend} |
### Customer Segments
| Segment | Size | Growth | WTP Signal | Priority |
|---------|------|--------|------------|----------|
| {name} | {size} | {rate} | {signal} | {Primary/Secondary/Tertiary} |
### Key Risks and Assumptions
| # | Assumption | Impact if Wrong | Confidence |
|---|-----------|-----------------|------------|
| 1 | {assumption} | {impact} | {High/Medium/Low} |
### Data Quality Assessment
| Data Point | Source | Date | Quality |
|-----------|--------|------|---------|
| {metric} | {source} | {date} | {Verified/Estimated/Extrapolated} |
### Recommendation
{1-2 paragraphs: proceed/pivot/investigate further, with specific next steps.}
| Score | Meaning | Criteria | | ----- | ----------- | ------------------------------------------------------------------------------------ | | 5 | Exceptional | Large TAM (> $10B), growing (> 15% CAGR), early adoption stage, regulatory tailwinds | | 4 | Strong | Large TAM or high growth, favorable timing, manageable competition | | 3 | Moderate | Mid-size market, moderate growth, competitive but differentiation possible | | 2 | Challenging | Small or saturated market, mature stage, significant headwinds | | 1 | Unfavorable | Declining market, regulatory barriers, limited differentiation |
| Problem | Resolution | | ----------------------------------- | -------------------------------------------------------------------------------------- | | No market data available | Use proxy markets and analogies. State the proxy explicitly. Reduce confidence to Low. | | Input too vague to size | Ask clarifying questions (target customer, geography, price point) before proceeding. | | Conflicting data sources | Present both figures, explain the discrepancy, use the more conservative estimate. | | Market is too new for reliable data | Size the adjacent market the product displaces. Note the nascent stage. | | User wants a single TAM number | Provide the range (conservative to optimistic) with the methodology behind each bound. |
Push back if:
testing
Manages dependent branch stacks and stacked pull requests using safe Git topology rules. Triggers on: "create stacked PRs", "publish this stack", "sync my PR stack", "rebase this stack", "merge the stack", "retarget child PRs", "split this branch into stacked PRs", "validate this stack", "cleanup stacked branches". Use when local branches or one source branch need to become a dependency-ordered PR stack with correct parent bases, validation, synchronization, merge order, and cleanup.
development
Scaffolds per-repository agent context so coding agents share the same issue tracker rules, triage label vocabulary, domain glossary, ADR layout, and handoff conventions. Triggers on: "set up project context", "configure agent docs", "create CONTEXT.md", "setup agent workflow", "agent issue tracker setup", "triage labels", "domain glossary for agents". Use when a repo needs durable context files before planning, triage, debugging, TDD, architecture review, or multi-agent implementation.
testing
Produces phased task boards from feature requests: dependency-mapped work items, parallelization flags, risk flags, edge cases, test matrices. Triggers on: "decompose this feature", "task breakdown with dependencies", "phased implementation plan", "work breakdown structure". NOT for effort estimates, use estimate-calibrator.
development
Hypothesis-driven debugging with ranked hypotheses, git bisect strategy, instrumentation planning, and minimal reproduction design. Triggers on: "debug this systematically", "root cause analysis", "bisect this bug", "rank hypotheses", "isolate this issue", "minimal reproduction". NOT for general reasoning.