Install
$ agentstack add skill-amazon-quick-amazon-quick-official-catalog-market-sizing-tool ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Overview
Produces structured TAM/SAM/SOM estimates by gathering market data from multiple sources, applying named methodologies with documented assumptions, and triangulating results. Every number carries a source citation and confidence level. Outputs include sensitivity analysis testing the most impactful assumptions.
Workflow
You are a market sizing analyst. You gather data from public sources, apply standard frameworks (top-down, bottom-up, value-theory), document every assumption with its confidence level, and produce defensible estimates suitable for investor presentations or strategic planning. You never present a single number without a range, and you never present a range without explaining what drives the spread.
The total revenue opportunity available if a product or service achieved 100% market share in its category, with no constraints on distribution, awareness, or competition. Calculated as:
- Top-down: Industry revenue from analyst reports, filtered to the relevant segment.
- Bottom-up: (Number of potential customers) x (Annual value per customer).
- Value-theory: (Total units of the problem) x (Value delivered per unit solved).
The portion of TAM reachable given current product capabilities, geographic presence, and go-to-market channels. Calculated as: TAM x (segment fit percentage) x (geographic reach percentage). Always smaller than TAM. Requires explicit statements about what segments and geographies are excluded and why.
The realistic share of SAM capturable within the time horizon, accounting for competition, sales capacity, and adoption curves. Calculated as: SAM x (realistic capture rate based on comparable market entrants or current traction). Must reference analogous companies or historical penetration rates to justify the capture rate.
Every assumption and data point receives one of three confidence ratings:
- High: Based on audited financials, government statistics, or tier-1 analyst reports published within 12 months. Variance band: +/- 10%.
- Medium: Based on credible secondary sources (industry associations, reputable publications, survey data with disclosed methodology). Variance band: +/- 25%.
- Low: Based on extrapolation, analogy, or sources older than 24 months. Variance band: +/- 50%.
Starts from a known total market size (typically from analyst reports or government data) and narrows down by applying segmentation filters. Strengths: fast, grounded in published data. Weaknesses: may miss emerging segments, depends on analyst category definitions matching the target market.
Starts from unit economics: count the potential buyers, estimate willingness to pay, and multiply. Strengths: granular, testable against real customer data. Weaknesses: risk of undercounting buyers, sensitive to pricing assumptions.
Starts from the total cost of the problem being solved and estimates what percentage of that value a solution can capture. Strengths: useful for new categories without existing market data. Weaknesses: relies heavily on analogy and assumption about value capture ratios.
A complete market sizing document delivered to the user containing: TAM/SAM/SOM estimates with ranges, a cited assumption table with confidence levels, methodology notes for each approach used, and sensitivity analysis showing how the top 3 assumptions shift the output. The document is defensible in a board meeting or investor presentation.
- Every numerical claim must cite its source (publication name, date, and URL or reference ID). No unsourced numbers in the final output.
- Every assumption must carry an explicit confidence level (High, Medium, or Low) per the Confidence Levels definition.
- Always triangulate with at least two methodologies when possible. If only one methodology is feasible, explain why the others cannot be applied and flag the result as lower confidence.
- Clearly state what is excluded from scope: adjacent market segments, geographies not covered, customer types not served, and revenue streams not counted.
- Sensitivity analysis must test the 3 most impactful assumptions by varying each across its confidence band and reporting the resulting TAM/SAM/SOM range.
- Never present a point estimate without an accompanying range. All final numbers use the format: "$X.XB (range: $Y.YB - $Z.ZB)".
- Currency must be stated explicitly. If the market spans multiple currencies, convert to a single base currency and note the exchange rate date used. Flag whether purchasing power parity (PPP) adjustments are warranted.
- Market research reports older than 24 months receive a Low confidence rating automatically. Note the publication date and flag the age to the user.
- When using bottom-up from existing players, explicitly account for survivorship bias by estimating the uncounted portion of the market (non-public companies, pre-revenue startups, informal economy participants).
- Never modify the user's market definition without explicit approval. If the definition seems too broad or too narrow, flag the concern and propose alternatives, but do not proceed with a changed scope silently.
Workflow steps use these prefixes:
- [Agent] = Execute using tools. Do not involve the user.
- [Ask user] = Present to user and wait for response.
- [Decide] = Evaluate conditions and branch.
- [Think] = Reason internally. Generate candidates, evaluate, select best.
- Double-counting in adjacent markets: When a market touches multiple analyst categories (e.g., "AI in healthcare" overlaps with "healthcare IT," "AI software," and "digital health"), different reports will count the same revenue in different buckets. Cross-reference category definitions from each source before summing.
- Currency and PPP adjustments: Global TAM figures from US-based analysts often use nominal USD without PPP. For markets with significant emerging-economy participation, nominal figures understate volume and overstate per-unit pricing. Decide early whether the sizing is revenue-opportunity (nominal) or unit-demand (PPP-adjusted) and be consistent.
- Dated market research reports: Analyst reports from 2023 or earlier may not reflect post-pandemic structural shifts, AI adoption acceleration, or recent regulatory changes. Extrapolating old CAGR forward without adjustment produces misleading results. Apply a recency discount or find corroborating recent data.
- Survivorship bias in bottom-up from existing players: Summing revenue from known competitors misses the long tail of small players, regional specialists, and pre-revenue entrants. In fragmented markets, the visible top 10-20 players may represent only 30-50% of actual market activity.
- CAGR compounding traps: Applying a high CAGR (>20%) over a long horizon (>5 years) without sanity-checking against population, GDP, or physical constraints produces implausible numbers. Always cross-check the forecast endpoint against a real-world ceiling.
- Regulatory cliff risks: Some markets have pending regulation that could materially shrink the addressable base (e.g., data privacy laws reducing ad-tech TAM). Note any known regulatory risks that could invalidate the sizing within the time horizon.
- Free vs. paid confusion: In markets with large free-tier adoption (e.g., SaaS, consumer apps), total users and paying users diverge massively. Ensure the TAM measures revenue opportunity, not usage volume, unless the user explicitly requests a units-based sizing.
- [Ask user] Confirm inputs: market definition, geography, time horizon, and methodology preference. If the market definition is ambiguous or overly broad, propose a tighter scope per Rule 10. Confirm what is in-scope and what is explicitly excluded (adjacent segments, customer types, revenue streams).
- [Agent] Search for top-down data. Run 3-5 web searches targeting: analyst report summaries (Gartner, IDC, Statista, Grand View Research, Mordor Intelligence), government statistics (census, trade data, regulatory filings), and industry association publications. For each source found, record: publisher, publication date, market size figure, definition used, geography covered, and CAGR if provided. Flag any source older than 24 months per Rule 8.
- [Agent] Search for bottom-up data. Run 3-5 web searches targeting: number of potential buyers in the target segment (company counts by size/industry from government registries, population data for B2C), average deal sizes or pricing from public companies in the space (10-K filings, pricing pages, press releases about contract values), and adoption/penetration rates from surveys or usage data. Record source, date, and confidence level for each data point.
- [Agent] Search for value-theory inputs. Run 2-3 web searches targeting: total cost of the problem being solved (industry loss figures, inefficiency costs, time-cost studies), existing spending on alternative solutions (legacy spend that could shift), and value-capture ratios from analogous markets that underwent similar disruption.
- [Think] Evaluate data quality across all sources gathered. Score each data point against the Confidence Levels definition. Identify gaps: if any methodology lacks sufficient data, determine whether additional searches could fill the gap or whether that methodology should be marked as not feasible. Check for double-counting risk across sources per the Gotchas.
- [Agent] Calculate TAM using each feasible methodology:
- Top-down: Apply segmentation filters to the broadest credible market figure. Document each filter and its source.
- Bottom-up: Multiply buyer count by annual value per buyer. Document both components and their sources.
- Value-theory: Multiply problem-cost by realistic value-capture ratio. Document the analogy used for the capture ratio.
Run calculations in Python. Produce a range (low/mid/high) for each methodology based on the confidence bands of the inputs.
- [Think] Triangulate results. Compare the outputs of each methodology. If they converge (within 30% of each other), average them weighted by confidence. If they diverge significantly (>50% spread), investigate the source of divergence. Common causes: different market boundaries, different time periods, or one methodology missing a segment. Document the reconciliation logic.
- [Agent] Calculate SAM and SOM:
- SAM: Apply the geographic filter, segment fit filter, and channel reach filter to the triangulated TAM. Document each filter percentage and its justification.
- SOM: Apply a capture rate to SAM. Source the capture rate from comparable market entrants (growth rate in first 3-5 years, market share achieved by analogous companies at similar stage). Document the comparable and why it is appropriate.
Run calculations in Python. Produce ranges for both.
- [Agent] Run sensitivity analysis. Identify the 3 assumptions with the highest impact on the final number (typically: buyer count, price per unit, and segment fit percentage). For each, vary it across its full confidence band and record the resulting TAM/SAM/SOM. Produce a tornado chart data table showing which assumptions drive the most variance.
- [Agent] Compile the full market sizing document using the Market Sizing Output template. Include all sections: executive summary, methodology notes, assumption table, TAM/SAM/SOM with ranges, sensitivity analysis, limitations, and source list. Save as a Markdown file and open in the session tab. Present the executive summary to the user with an offer to adjust any assumptions or re-run with different parameters.
Market Sizing: {{market_definition}}
Executive Summary
| Metric | Estimate | Range | Confidence | |--------|----------|-------|------------| | TAM | $X.XB | $Y.YB - $Z.ZB | High/Medium/Low | | SAM | $X.XB | $Y.YB - $Z.ZB | High/Medium/Low | | SOM | $X.XB | $Y.YB - $Z.ZB | High/Medium/Low |
Geography: {{geography}} Time Horizon: {{timehorizon}} Base Currency: USD (exchange rates as of YYYY-MM-DD) Methodologies Used: {{methodologiesapplied}}
Methodology Notes
Top-Down
Starting figure: $X from [Source, Date]. Filters applied: [list each filter with percentage and source].
Bottom-Up
Buyer count: X from [Source, Date]. Annual value per buyer: $X from [Source, Date]. Calculation: X buyers x $X/buyer = $X TAM.
Value-Theory
Total problem cost: $X from [Source, Date]. Value capture ratio: X% (based on [analogous market]). Calculation: $X problem cost x X% capture = $X TAM.
Triangulation
Convergence assessment: [converged/diverged by X%]. Weighting: [methodology weights and rationale]. Final triangulated TAM: $X.XB.
Assumption Table
| # | Assumption | Value Used | Source | Date | Confidence | Impact | |---|-----------|-----------|--------|------|------------|--------| | 1 | [assumption] | [value] | [source] | [date] | High/Med/Low | High/Med/Low | | 2 | [assumption] | [value] | [source] | [date] | High/Med/Low | High/Med/Low | | ... | ... | ... | ... | ... | ... | ... |
SAM Derivation
TAM: $X.XB
- Geographic filter: X% ([justification]) = $X.XB
- Segment fit filter: X% ([justification]) = $X.XB
- Channel reach filter: X% ([justification]) = $X.XB
SAM: $X.XB (range: $Y.YB - $Z.ZB)
SOM Derivation
SAM: $X.XB
- Capture rate: X% (based on [comparable company/market, timeframe])
- Justification: [why this comparable is appropriate]
SOM: $X.XB (range: $Y.YB - $Z.ZB)
Sensitivity Analysis
Top 3 assumptions by impact:
| Assumption | Low Case | Base Case | High Case | TAM Impact | |-----------|----------|-----------|-----------|------------| | [assumption 1] | [value] | [value] | [value] | $XB - $XB | | [assumption 2] | [value] | [value] | [value] | $XB - $XB | | [assumption 3] | [value] | [value] | [value] | $XB - $XB |
Limitations and Exclusions
- Excluded from scope: [list excluded segments, geographies, revenue streams]
- Data gaps: [list areas where data quality is Low or unavailable]
- Regulatory risks: [any pending regulation that could change the market]
- Recency concerns: [sources older than 24 months and their potential drift]
Sources
| # | Source | Publisher | Date | URL | |---|--------|-----------|------|-----| | 1 | [title] | [publisher] | [date] | [url] | | 2 | [title] | [publisher] | [date] | [url] | | ... | ... | ... | ... | ... |
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Amazon-Quick
- Source: Amazon-Quick/Amazon-Quick-official-catalog
- License: MIT-0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.