Update to Data
Snapshot Nov 13, 2026 · 18:09 UTC · version 1.2.0
Collection source: downloaded plugin package.
Payment or plan references changed
Skill instructions — Now says: Test a downside that could change the recommendation. For pricing or migration, incremental revenue may be negative: separate the signed change from the...
Observed in published text. Live prices and checkout terms have not been verified by this change.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Oct 27, 2026 · 06:06 UTC
For an inline answer, follow [inline delivery](../index/SKILL.md#inline-delivery) for charts and proportionate Sources delivery.
Nov 13, 2026 · 18:09 UTC
Test a downside that could change the recommendation. For pricing or migration, incremental revenue may be negative: separate the signed change from the existing price, additional spend, and displaced revenue instead of forcing every mon...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -89,11 +89,13 @@ Use ranges when uncertainty is material. Do not hide uncertainty behind a single point estimate when the inputs are thin. +Test a downside that could change the recommendation. For pricing or migration, incremental revenue may be negative: separate the signed change from the existing price, additional spend, and displaced revenue instead of forcing every monetary input or output to be nonnegative. Keep displaced revenue as a subtraction even when the price change is negative. If the evidence raises discounting or cannibalization, carry that possibility through the model, control bounds and chart axes; a low but still profitable preset does not test a loss scenario. Label the assumptions and check that downside, zero population and reset agree across the report and tool. + ### 7. State The Estimate And Validation Priorities Return the estimate, method, key assumptions, uncertainty, and next validation priorities using the [selected presentation](../index/SKILL.md#output-and-presentation). -For an inline answer, follow [inline delivery](../index/SKILL.md#inline-delivery) for charts and proportionate Sources delivery. +Follow the selected presentation. In chat, use Visualize directly for a useful chart. Include inspectable sources when scope or processing materially affects the answer. Before handoff, make the market-sizing conclusion explicit:
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: market-sizing\ndescription: \"Estimate market, segment, or opportunity size with transparent assumptions and uncertainty. Use for TAM/SAM/SOM, sizing scenarios, or comparing the scale of possible opportunities.\"\n---\n\n# Market Sizing\n\nUse this skill to produce a defensible estimate of a market or opportunity from connected context, public sources, transparent assumptions, and auditable calculations. The job is to define the market, choose a sound sizing method, distinguish evidence from assumptions, test sensitivity, and state what would most improve confidence.\n\n## Overall Instructions\n\n- Before choosing or changing the deliverable, apply [presentation routing](../index/SKILL.md#output-and-presentation). For consequential missing details, use [task intake](../../shared/task-intake.md). Before quantitative claims, apply [analysis quality](../../shared/analysis-quality.md); resolve company-specific meaning through [metric definitions](../../shared/metric-definitions.md) before choosing the controlling source.\n- Apply the [shared Data instructions](../../shared/shared-skill-instructions.md) and the shared guidance referenced below. Use instructions already loaded for this task, including by the index or another skill; read only what is missing.\n\n## Dependencies\n\nBefore selecting evidence, apply [source selection and dependency resolution](../../shared/source-selection.md) to the categories below.\n\n- Knowledge & Files: Market research, source publications, assumptions, and supplied sizing models.\n- Data Warehouse: Company-specific customer, revenue, adoption, and segment inputs.\n- Business Intelligence: Governed segment reports and existing market or business benchmarks.\n- Product Analytics: Usage and adoption evidence for estimating reachable segments and opportunity.\n\n## Related Skills\n\nPass chart-ready evidence to the selected response mode.\n\nUse [task intake](../../shared/task-intake.md) for proceeding, asking while working, and waiting. The planning steps below guide the analysis; they are not a questionnaire.\n\n## Workflow\n\n### 1. Frame The Market Or Opportunity\n\nDefine the market or opportunity boundary before estimating:\n\n- What is being sized, for example a product category, workflow, problem, use case, or category of activity.\n- Where and when it applies, for example geography, segment scope, time horizon, or market maturity.\n- Who or what counts as part of the market, for example the relevant population, unit of demand, transaction type, or included activity.\n- How the opportunity is measured, for example spend, revenue, volume, value created, or another unit that fits the question.\n- What kind of sizing answer the user needs, for example TAM/SAM/SOM, market entry, expansion upside, spend pool, revenue pool, population count, or unit volume.\n\n### 2. Choose A Starting Sizing Approach And Inputs\n\nPick the simplest sound sizing approach for the question, then sketch the calculation chain and the major inputs the estimate will depend on.\n\nA top-down model works when reliable aggregate market data exists; a bottom-up model works when the market can be built from observable units and assumptions; a value-based model works when the estimate should start from the value created rather than a published market total. Use a mixed approach only when cross-checking would materially improve confidence. If more than one approach fits, briefly explain which one you trust most and why.\n\nExpect the first approach to change if source checks show that another model would be more defensible.\n\n### 3. Gather Sources For The Inputs\n\nChoose sources based on the inputs the estimate depends on most.\n\nStart with user-named sources when provided. Then use the strongest available evidence for each major input from the starting approach. Use `~~structured_data` when an input should come from the user's data warehouse or another structured data source. Use context lanes such as `~~company_docs`, `~~team_communication`, or `~~dashboards_or_bi` when an input needs business meaning, source-of-truth guidance, or assumptions that are not captured in structured data alone. When an input depends on the outside market, use public sources for benchmarks, population estimates, comparable markets, or proxy assumptions.\n\nWhen the right source of truth, business meaning, or assumption set is unclear, follow the shared [Authoritative metrics and definitions](../../shared/metric-definitions.md) and [business context](../../shared/metric-definitions.md#business-context) guidance.\n\nIf the strongest source is unavailable or thin, continue with a transparent proxy assumption only when the estimate is still useful. Label the gap and explain how it affects confidence.\n\n### 4. Separate Facts From Assumptions\n\nKeep sourced facts, inferred estimates, and judgment calls distinct in the model. When exact data is unavailable, use a defensible proxy, explain why it is reasonable, and note the confidence level. Ground assumptions in evidence about how the market actually behaves, what can realistically change, and what determines the size of the opportunity.\n\n### 5. Build The Model\n\nMake the model easy to inspect and adjust.\n\nThe model should make these elements easy to audit or revise:\n\n- market definition and measurement unit\n- assumptions and source context\n- calculation chain and derived values\n- base case, material ranges, and sensitivity logic\n- validation priorities\n\nFor each major input, make the source path visible: structured data, context lane, public source, user-provided input, or proxy assumption.\n\nKeep derived values traceable to formulas or code rather than hardcoded outputs.\n\nKeep formulas, inputs, intermediate calculations and sensitivity logic inspectable under the shared [analysis-record policy](../../shared/shared-skill-instructions.md#analysis-records-and-companion-artifacts).\n\nUse the `$Spreadsheets` skill when the user requests a spreadsheet, workbook or Google Sheets deliverable.\n\n### 6. Test Sensitivity\n\nIdentify the assumptions that move the estimate most.\n\nShow how the estimate changes when those assumptions move up or down. Prefer simple, decision-useful sensitivity analysis over exhaustive scenario sprawl.\n\nUse ranges when uncertainty is material. Do not hide uncertainty behind a single point estimate when the inputs are thin.\n\n### 7. State The Estimate And Validation Priorities\n\nReturn the estimate, method, key assumptions, uncertainty, and next validation priorities using the [selected presentation](../index/SKILL.md#output-and-presentation).\n\nFor an inline answer, follow [inline delivery](../index/SKILL.md#inline-delivery) for charts and proportionate Sources delivery.\n\nBefore handoff, make the market-sizing conclusion explicit:\n\n- market definition and measurement unit\n- estimate or range\n- method and calculation chain\n- key assumptions and source support\n- main uncertainty drivers and sensitivity takeaways\n- validation priorities and practical interpretation for the user's decision\n\nIf source coverage is thin, say which major inputs rely on proxy assumptions and what source would most improve them.\n\nBefore sharing, apply the shared [analysis quality criteria](../../shared/analysis-quality.md) to methodology, calculations, assumptions, caveats, and source support within this workflow.\n\nPass sensitivity, scenario, funnel, or market-breakdown visual intent and supporting evidence to the selected response mode.\n"
"---\nname: market-sizing\ndescription: \"Estimate market, segment, or opportunity size with transparent assumptions and uncertainty. Use for TAM/SAM/SOM, sizing scenarios, or comparing the scale of possible opportunities.\"\n---\n\n# Market Sizing\n\nUse this skill to produce a defensible estimate of a market or opportunity from connected context, public sources, transparent assumptions, and auditable calculations. The job is to define the market, choose a sound sizing method, distinguish evidence from assumptions, test sensitivity, and state what would most improve confidence.\n\n## Overall Instructions\n\n- Before choosing or changing the deliverable, apply [presentation routing](../index/SKILL.md#output-and-presentation). For consequential missing details, use [task intake](../../shared/task-intake.md). Before quantitative claims, apply [analysis quality](../../shared/analysis-quality.md); resolve company-specific meaning through [metric definitions](../../shared/metric-definitions.md) before choosing the controlling source.\n- Apply the [shared Data instructions](../../shared/shared-skill-instructions.md) and the shared guidance referenced below. Use instructions already loaded for this task, including by the index or another skill; read only what is missing.\n\n## Dependencies\n\nBefore selecting evidence, apply [source selection and dependency resolution](../../shared/source-selection.md) to the categories below.\n\n- Knowledge & Files: Market research, source publications, assumptions, and supplied sizing models.\n- Data Warehouse: Company-specific customer, revenue, adoption, and segment inputs.\n- Business Intelligence: Governed segment reports and existing market or business benchmarks.\n- Product Analytics: Usage and adoption evidence for estimating reachable segments and opportunity.\n\n## Related Skills\n\nPass chart-ready evidence to the selected response mode.\n\nUse [task intake](../../shared/task-intake.md) for proceeding, asking while working, and waiting. The planning steps below guide the analysis; they are not a questionnaire.\n\n## Workflow\n\n### 1. Frame The Market Or Opportunity\n\nDefine the market or opportunity boundary before estimating:\n\n- What is being sized, for example a product category, workflow, problem, use case, or category of activity.\n- Where and when it applies, for example geography, segment scope, time horizon, or market maturity.\n- Who or what counts as part of the market, for example the relevant population, unit of demand, transaction type, or included activity.\n- How the opportunity is measured, for example spend, revenue, volume, value created, or another unit that fits the question.\n- What kind of sizing answer the user needs, for example TAM/SAM/SOM, market entry, expansion upside, spend pool, revenue pool, population count, or unit volume.\n\n### 2. Choose A Starting Sizing Approach And Inputs\n\nPick the simplest sound sizing approach for the question, then sketch the calculation chain and the major inputs the estimate will depend on.\n\nA top-down model works when reliable aggregate market data exists; a bottom-up model works when the market can be built from observable units and assumptions; a value-based model works when the estimate should start from the value created rather than a published market total. Use a mixed approach only when cross-checking would materially improve confidence. If more than one approach fits, briefly explain which one you trust most and why.\n\nExpect the first approach to change if source checks show that another model would be more defensible.\n\n### 3. Gather Sources For The Inputs\n\nChoose sources based on the inputs the estimate depends on most.\n\nStart with user-named sources when provided. Then use the strongest available evidence for each major input from the starting approach. Use `~~structured_data` when an input should come from the user's data warehouse or another structured data source. Use context lanes such as `~~company_docs`, `~~team_communication`, or `~~dashboards_or_bi` when an input needs business meaning, source-of-truth guidance, or assumptions that are not captured in structured data alone. When an input depends on the outside market, use public sources for benchmarks, population estimates, comparable markets, or proxy assumptions.\n\nWhen the right source of truth, business meaning, or assumption set is unclear, follow the shared [Authoritative metrics and definitions](../../shared/metric-definitions.md) and [business context](../../shared/metric-definitions.md#business-context) guidance.\n\nIf the strongest source is unavailable or thin, continue with a transparent proxy assumption only when the estimate is still useful. Label the gap and explain how it affects confidence.\n\n### 4. Separate Facts From Assumptions\n\nKeep sourced facts, inferred estimates, and judgment calls distinct in the model. When exact data is unavailable, use a defensible proxy, explain why it is reasonable, and note the confidence level. Ground assumptions in evidence about how the market actually behaves, what can realistically change, and what determines the size of the opportunity.\n\n### 5. Build The Model\n\nMake the model easy to inspect and adjust.\n\nThe model should make these elements easy to audit or revise:\n\n- market definition and measurement unit\n- assumptions and source context\n- calculation chain and derived values\n- base case, material ranges, and sensitivity logic\n- validation priorities\n\nFor each major input, make the source path visible: structured data, context lane, public source, user-provided input, or proxy assumption.\n\nKeep derived values traceable to formulas or code rather than hardcoded outputs.\n\nKeep formulas, inputs, intermediate calculations and sensitivity logic inspectable under the shared [analysis-record policy](../../shared/shared-skill-instructions.md#analysis-records-and-companion-artifacts).\n\nUse the `$Spreadsheets` skill when the user requests a spreadsheet, workbook or Google Sheets deliverable.\n\n### 6. Test Sensitivity\n\nIdentify the assumptions that move the estimate most.\n\nShow how the estimate changes when those assumptions move up or down. Prefer simple, decision-useful sensitivity analysis over exhaustive scenario sprawl.\n\nUse ranges when uncertainty is material. Do not hide uncertainty behind a single point estimate when the inputs are thin.\n\nTest a downside that could change the recommendation. For pricing or migration, incremental revenue may be negative: separate the signed change from the existing price, additional spend, and displaced revenue instead of forcing every monetary input or output to be nonnegative. Keep displaced revenue as a subtraction even when the price change is negative. If the evidence raises discounting or cannibalization, carry that possibility through the model, control bounds and chart axes; a low but still profitable preset does not test a loss scenario. Label the assumptions and check that downside, zero population and reset agree across the report and tool.\n\n### 7. State The Estimate And Validation Priorities\n\nReturn the estimate, method, key assumptions, uncertainty, and next validation priorities using the [selected presentation](../index/SKILL.md#output-and-presentation).\n\nFollow the selected presentation. In chat, use Visualize directly for a useful chart. Include inspectable sources when scope or processing materially affects the answer.\n\nBefore handoff, make the market-sizing conclusion explicit:\n\n- market definition and measurement unit\n- estimate or range\n- method and calculation chain\n- key assumptions and source support\n- main uncertainty drivers and sensitivity takeaways\n- validation priorities and practical interpretation for the user's decision\n\nIf source coverage is thin, say which major inputs rely on proxy assumptions and what source would most improve them.\n\nBefore sharing, apply the shared [analysis quality criteria](../../shared/analysis-quality.md) to methodology, calculations, assumptions, caveats, and source support within this workflow.\n\nPass sensitivity, scenario, funnel, or market-breakdown visual intent and supporting evidence to the selected response mode.\n"
Full snapshot data
{
"description": "Estimate market, segment, or opportunity size with transparent assumptions and uncertainty. Use for TAM/SAM/SOM, sizing scenarios, or comparing the scale of possible opportunities.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 300
}
],
"name": "market-sizing",
"skill_md_contents": "---\nname: market-sizing\ndescription: \"Estimate market, segment, or opportunity size with transparent assumptions and uncertainty. Use for TAM/SAM/SOM, sizing scenarios, or comparing the scale of possible opportunities.\"\n---\n\n# Market Sizing\n\nUse this skill to produce a defensible estimate of a market or opportunity from connected context, public sources, transparent assumptions, and auditable calculations. The job is to define the market, choose a sound sizing method, distinguish evidence from assumptions, test sensitivity, and state what would most improve confidence.\n\n## Overall Instructions\n\n- Before choosing or changing the deliverable, apply [presentation routing](../index/SKILL.md#output-and-presentation). For consequential missing details, use [task intake](../../shared/task-intake.md). Before quantitative claims, apply [analysis quality](../../shared/analysis-quality.md); resolve company-specific meaning through [metric definitions](../../shared/metric-definitions.md) before choosing the controlling source.\n- Apply the [shared Data instructions](../../shared/shared-skill-instructions.md) and the shared guidance referenced below. Use instructions already loaded for this task, including by the index or another skill; read only what is missing.\n\n## Dependencies\n\nBefore selecting evidence, apply [source selection and dependency resolution](../../shared/source-selection.md) to the categories below.\n\n- Knowledge & Files: Market research, source publications, assumptions, and supplied sizing models.\n- Data Warehouse: Company-specific customer, revenue, adoption, and segment inputs.\n- Business Intelligence: Governed segment reports and existing market or business benchmarks.\n- Product Analytics: Usage and adoption evidence for estimating reachable segments and opportunity.\n\n## Related Skills\n\nPass chart-ready evidence to the selected response mode.\n\nUse [task intake](../../shared/task-intake.md) for proceeding, asking while working, and waiting. The planning steps below guide the analysis; they are not a questionnaire.\n\n## Workflow\n\n### 1. Frame The Market Or Opportunity\n\nDefine the market or opportunity boundary before estimating:\n\n- What is being sized, for example a product category, workflow, problem, use case, or category of activity.\n- Where and when it applies, for example geography, segment scope, time horizon, or market maturity.\n- Who or what counts as part of the market, for example the relevant population, unit of demand, transaction type, or included activity.\n- How the opportunity is measured, for example spend, revenue, volume, value created, or another unit that fits the question.\n- What kind of sizing answer the user needs, for example TAM/SAM/SOM, market entry, expansion upside, spend pool, revenue pool, population count, or unit volume.\n\n### 2. Choose A Starting Sizing Approach And Inputs\n\nPick the simplest sound sizing approach for the question, then sketch the calculation chain and the major inputs the estimate will depend on.\n\nA top-down model works when reliable aggregate market data exists; a bottom-up model works when the market can be built from observable units and assumptions; a value-based model works when the estimate should start from the value created rather than a published market total. Use a mixed approach only when cross-checking would materially improve confidence. If more than one approach fits, briefly explain which one you trust most and why.\n\nExpect the first approach to change if source checks show that another model would be more defensible.\n\n### 3. Gather Sources For The Inputs\n\nChoose sources based on the inputs the estimate depends on most.\n\nStart with user-named sources when provided. Then use the strongest available evidence for each major input from the starting approach. Use `~~structured_data` when an input should come from the user's data warehouse or another structured data source. Use context lanes such as `~~company_docs`, `~~team_communication`, or `~~dashboards_or_bi` when an input needs business meaning, source-of-truth guidance, or assumptions that are not captured in structured data alone. When an input depends on the outside market, use public sources for benchmarks, population estimates, comparable markets, or proxy assumptions.\n\nWhen the right source of truth, business meaning, or assumption set is unclear, follow the shared [Authoritative metrics and definitions](../../shared/metric-definitions.md) and [business context](../../shared/metric-definitions.md#business-context) guidance.\n\nIf the strongest source is unavailable or thin, continue with a transparent proxy assumption only when the estimate is still useful. Label the gap and explain how it affects confidence.\n\n### 4. Separate Facts From Assumptions\n\nKeep sourced facts, inferred estimates, and judgment calls distinct in the model. When exact data is unavailable, use a defensible proxy, explain why it is reasonable, and note the confidence level. Ground assumptions in evidence about how the market actually behaves, what can realistically change, and what determines the size of the opportunity.\n\n### 5. Build The Model\n\nMake the model easy to inspect and adjust.\n\nThe model should make these elements easy to audit or revise:\n\n- market definition and measurement unit\n- assumptions and source context\n- calculation chain and derived values\n- base case, material ranges, and sensitivity logic\n- validation priorities\n\nFor each major input, make the source path visible: structured data, context lane, public source, user-provided input, or proxy assumption.\n\nKeep derived values traceable to formulas or code rather than hardcoded outputs.\n\nKeep formulas, inputs, intermediate calculations and sensitivity logic inspectable under the shared [analysis-record policy](../../shared/shared-skill-instructions.md#analysis-records-and-companion-artifacts).\n\nUse the `$Spreadsheets` skill when the user requests a spreadsheet, workbook or Google Sheets deliverable.\n\n### 6. Test Sensitivity\n\nIdentify the assumptions that move the estimate most.\n\nShow how the estimate changes when those assumptions move up or down. Prefer simple, decision-useful sensitivity analysis over exhaustive scenario sprawl.\n\nUse ranges when uncertainty is material. Do not hide uncertainty behind a single point estimate when the inputs are thin.\n\nTest a downside that could change the recommendation. For pricing or migration, incremental revenue may be negative: separate the signed change from the existing price, additional spend, and displaced revenue instead of forcing every monetary input or output to be nonnegative. Keep displaced revenue as a subtraction even when the price change is negative. If the evidence raises discounting or cannibalization, carry that possibility through the model, control bounds and chart axes; a low but still profitable preset does not test a loss scenario. Label the assumptions and check that downside, zero population and reset agree across the report and tool.\n\n### 7. State The Estimate And Validation Priorities\n\nReturn the estimate, method, key assumptions, uncertainty, and next validation priorities using the [selected presentation](../index/SKILL.md#output-and-presentation).\n\nFollow the selected presentation. In chat, use Visualize directly for a useful chart. Include inspectable sources when scope or processing materially affects the answer.\n\nBefore handoff, make the market-sizing conclusion explicit:\n\n- market definition and measurement unit\n- estimate or range\n- method and calculation chain\n- key assumptions and source support\n- main uncertainty drivers and sensitivity takeaways\n- validation priorities and practical interpretation for the user's decision\n\nIf source coverage is thin, say which major inputs rely on proxy assumptions and what source would most improve them.\n\nBefore sharing, apply the shared [analysis quality criteria](../../shared/analysis-quality.md) to methodology, calculations, assumptions, caveats, and source support within this workflow.\n\nPass sensitivity, scenario, funnel, or market-breakdown visual intent and supporting evidence to the selected response mode.\n"
}SHA-256 of public snapshot: 33d796d7de8d7caff4fecd483c953efd9fa36331dea45288abf9805e8aecac53